env-setup

What This Skill Does

The env-setup skill is a powerful developer utility designed to bring order to your environment variable chaos. It acts as an automated audit tool for your codebase, scanning files for references to environment variables across multiple programming languages including JavaScript, TypeScript, Python, Rust, and Go. By parsing these references, it extracts unique variable names, categorizes them based on their sensitivity and function (Secrets, Service URLs, Configuration, and Others), and generates a clean, standardized .env.example file. This practice ensures your project documentation remains up-to-date and prevents the common mistake of committing hard-coded credentials to version control.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/fratua/env-setup

Use Cases

This skill is indispensable for onboarding new developers to a project, preparing a codebase for open-source publication, or auditing legacy repositories. It is particularly useful when you need to quickly identify which services a project depends on to function correctly. By automatically generating documentation for your dependencies, you minimize 'works on my machine' errors and provide a clear roadmap for setting up local or production environments.

Example Prompts

1. "Scan my current repository for all environment variables and generate an updated .env.example file."
2. "Analyze my project structure and identify which variables in my .env are categorized as sensitive secrets that shouldn't be committed."
3. "Please perform an environment audit on this codebase, grouping the variables by category and creating a template with sensible defaults."

Tips & Limitations

While env-setup is highly effective at identifying standard variable patterns, it relies on grep-based string matching. If your code uses highly dynamic or obfuscated ways of fetching environment variables (such as runtime assembly of key names), the tool might miss them. Always perform a quick manual review after generation, especially when dealing with production-grade secrets. Ensure that your .gitignore is configured correctly before running the skill to avoid accidental commits of your local .env file. The skill works best on projects with standard directory structures and will intelligently skip common noise folders like node_modules, .venv, and dist to save execution time.