- Home
- Skills
- DevOps & Cloud
- env file validator
env file validator
Automated .env file validation to catch missing or undocumented configuration variables without exposing secrets.
Free
Works with the AI Agents you already use
env file validator
Example session with this skill installed
Run the env validator in the current directory and let me know if my .env file is missing anything from .env.example. Use JSON format.
- Read your context and instructions
- Compiled the env file validator
I have analyzed your environment files. The validator compared .env.example against your local .env file and found that your configuration is incomplete.
Environment Validation Report
| Category | Variable Name | Status | Recommendation |
|---|---|---|---|
| Missing | STRIPE_SECRET_KEY | Required | Add to .env |
| Missing | AWS_REGION | Required | Add to .env |
| Undocumented | DEBUG_MODE | Extra | Add to .env.example or remove from .env |
| Optional | REDIS_URL | Absent | Optional (commented in template) |
The validation failed with
Exit Code 1 because required keys are missing. Your .env file currently contains 12 variables, but it is missing 2 required keys defined in the template. Additionally, you have 1 variable (DEBUG_MODE) that exists in your environment but isn't documented in your example file.
Next steps
- Add the missing
STRIPE_SECRET_KEYandAWS_REGIONto your.envfile. - If
DEBUG_MODEis required for the project, add it to.env.exampleto help other developers. - Run the validator again to confirm a clean exit code before pushing your changes.
Connects securely to your tools. The creator never sees your data.
About this skill
Applications crash on startup when developers forget to update their local .env files after a pull. This skill automates environment configuration audits, ensuring your local or production environment matches your project template without exposing sensitive values.
What it does
- Required key validation identifies variables present in the template but missing from the active environment.
- Template drift detection flags keys in the environment file that are not documented in the example file.
- Optional key reporting recognizes commented-out keys in templates as optional and tracks their status separately.
- Security-first parsing reads only variable names, ensuring secret values are never stored, displayed, or processed.
- CI/CD integration provides specific exit codes and strict modes to block builds when configuration is inconsistent.
How it works
- Auto-detection scans the directory for standard naming conventions like
.env.exampleand.env.production. - Comparison maps the key list from the template against the active file while ignoring values.
- Status reporting generates a text or JSON summary of missing, undocumented, and optional variables.
- Resolution guides the user to update their environment or document new variables in the template.
Frameworks & tools
This skill uses a standalone Python script compatible with Python 3.8+. It relies exclusively on the standard library, requiring no third-party dependencies like python-dotenv.
Why this beats prompting it yourself
Generic prompts often struggle with specific .env edge cases like inline comments or commented-out optional keys. This tool provides a dedicated parser that handles these nuances while guaranteeing zero exposure of your actual secrets to the LLM context.
Use cases
- Validate local environment setup during developer onboarding.
- Prevent deployment failures by checking production
.envfiles against templates. - Audit repositories for undocumented "shadow" environment variables.
- Automate configuration checks in pre-commit hooks or CI pipelines.
Known limitations
Does not support multi-line values, shell variable substitution, or the export prefix. Only standard KEY=value formats are parsed.
Requires Python 3.8+. No support for multi-line variables, shell substitution, or export syntax. Missing files or usage errors return exit code 2.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 3 days ago
- Free with an Agensi account
Requires