Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Env Var Missing Key Checker

    1

    Safely compare .env.example against your local .env, reveal missing or undocumented keys, and catch configuration drift without printing secret values.

    Free

    1 useSecurity scanned
    Env Var Missing Key Checker

    Env Var Missing Key Checker

    Example session with this skill installed

    Check whether my local environment file is missing any keys required by the project.

    Use
    .env.example
    .env

    Requirements

    • compare key names only;
    • never print or expose values from .env;
    • identify keys present in .env.example but missing from .env;
    • identify extra local keys that are not documented in .env.example;
    • detect duplicate keys;
    • detect malformed environment-variable lines;
    • ignore commented-out entries;
    • warn me if .env appears to be tracked by Git;
    • do not modify either file;
    • generate env_diff_report.md;
    • show the missing key names first and suggest the smallest safe next steps.
    • Read your context and instructions
    • Compiled the env var missing

    Environment variable check complete

    Status
    FAIL

    Files compared
    .env.example
    .env

    Missing keys
    2

    Extra undocumented keys
    1

    Duplicate keys
    0

    Malformed lines
    0

    .env tracked by Git:
    NO

    Missing keys

    • REDIS_URL
    • STRIPE_SECRET_KEY

    Extra local key

    • LOCAL_ONLY_FLAG

    This extra key is not automatically an error. It may be machine-specific or simply missing from project documentation.

    Security

    No .env values were included in the analysis output.

    Recommended next steps

    1. Add REDIS_URL to your local .env with the correct local value.
    2. Add STRIPE_SECRET_KEY locally using your development/test credential.
    3. Decide whether LOCAL_ONLY_FLAG should be documented in .env.example.

    Output

    Generated
    env_diff_report.md

    No environment files were modified.

    env_diff_report.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Find missing environment variables before runtime does

    A teammate adds a new environment variable, your local .env falls behind, and the application crashes later with an undefined or missing configuration error.

    Env Var Missing Key Checker compares the real files in your local project and shows exactly which variable names are missing—without exposing secret values.

    • Compares .env.example against .env
    • Reports missing keys instantly
    • Finds undocumented local keys
    • Detects duplicate declarations
    • Flags malformed environment-variable lines
    • Warns if .env appears to be tracked by Git
    • Never includes .env secret values in the generated report
    • Produces a clean Markdown remediation report

    Why use this instead of pasting .env into chat?

    You should not have to paste sensitive environment files into a conversation just to compare key names.

    This skill works against local files and deliberately reports only variable names and configuration issues.

    .env.example + .env → Key extraction → Safe diff → Security checks → Report

    Free by design

    This free checker focuses on configuration drift. Secret rotation, vault synchronization, credential validation, and enterprise secrets governance remain intentionally outside this lightweight workflow.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Does not validate if secret values are functionally correct. Only performs static analysis of key names. Requires local file system access.

    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 buying a skill.

    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

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed26 days ago

    What's inside

    Frequently Asked Questions

    The skill strictly extracts and parses key names only, immediately discarding the actual values assigned to them. This ensures your API keys and passwords never enter the LLM's context window or the generated reports.

    Yes, while it defaults to standard .env and .env.example files, you can provide custom paths for specific environments like .env.production or .env.staging.

    This skill is framework-agnostic and works with any project that utilizes key-value pair .env files, including those built with Node.js, Python, Ruby, Go, and PHP.

    The skill flags 'undocumented keys,' which are variables present in your local file but missing from the template, helping you keep your project's onboarding documentation up to date.

    No, this skill performs static analysis only; it checks for the existence and formatting of keys without connecting to your cloud provider or third-party services.

    Upon purchase, you receive the full skill package including the logic for key extraction, comparison reporting, and the git-safety auditing module.

    New in LLM Ops

    Free