env file validator

    1

    Automated .env file validation to catch missing or undocumented configuration variables without exposing secrets.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    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

    CategoryVariable NameStatusRecommendation
    MissingSTRIPE_SECRET_KEYRequiredAdd to .env
    MissingAWS_REGIONRequiredAdd to .env
    UndocumentedDEBUG_MODEExtraAdd to .env.example or remove from .env
    OptionalREDIS_URLAbsentOptional (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

    1. Add the missing STRIPE_SECRET_KEY and AWS_REGION to your .env file.
    2. If DEBUG_MODE is required for the project, add it to .env.example to help other developers.
    3. 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

    1. Auto-detection scans the directory for standard naming conventions like .env.example and .env.production.
    2. Comparison maps the key list from the template against the active file while ignoring values.
    3. Status reporting generates a text or JSON summary of missing, undocumented, and optional variables.
    4. 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 .env files 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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    This skill compares your active .env file against a template (like .env.example) to identify missing or undocumented keys, preventing application crashes caused by configuration drift.

    The skill uses a security-first parser that only reads variable names, ensuring your actual secret values are never processed, stored, or sent to the LLM.

    Yes, the skill provides specific exit codes and JSON reporting, making it easy to integrate into CI/CD pipelines or pre-commit hooks to block builds if configurations are incomplete.

    The skill is a standalone Python tool (3.8+) that uses the standard library, meaning it works out-of-the-box with any AI agent capable of executing Python scripts without needing extra dependencies.

    It supports standard KEY=value formats, including commented-out optional keys, but it does not currently support multi-line values, shell variable expansion, or the 'export' prefix.

    Your purchase includes the core validation script, documentation on integration, and lifetime access to any future logic updates or bug fixes.

    New in DevOps & Cloud