Validate required environment variables in .env files without exposing values.
npx skills add https://github.com/bettercallzaal/ZAOOS --skill check-env-bettercallzaal
Please help me install this Agent Skill. Skill: check-env Source: https://github.com/bettercallzaal/ZAOOS/tree/main/.claude/skills/check-env Command: npx skills add https://github.com/bettercallzaal/ZAOOS --skill check-env-bettercallzaal
Read .env.example and .env files to ensure required environment variables are present before deploying, without exposing their actual values.
Run the check-env validation after cloning or before deployment to verify that all required environment variables are present and non-empty without printing their values.
High-intent search queries and answers about installing and using this skill.
To validate environment variables safely before deployment, compare required keys from your .env.example against the active environment file, checking for missing or empty values without printing the actual sensitive data.
Validating .env configuration after a fresh clone involves reading the .env.example file to identify required keys and verifying their presence in the active environment to ensure all necessary variables are set and non-empty.
Yes, you can debug connection issues by enforcing configuration correctness, which reports a concise summary of configured versus missing keys while ensuring that required variables are marked as Set, Missing, or Empty without revealing values.
Environment variable validation works across dev, staging, and prod by validating the presence of required environment variables in the active environment file against the defined .env.example template for that specific context.
Environment variables show as empty during pre-deploy checks when the keys exist in the active environment file but lack assigned values, which the validation process identifies to enforce configuration correctness before deployment.
SumitRajpalScan TypeScript/JavaScript code for process.env usage and report missing or unused keys against .env.example.
MaciWPValidate environment variables with type-safe schemas at application startup.
HomericIntelligenceRun Mojo format, markdownlint, and pre-commit hooks for code quality checks.
MacPhobosDefine TypeScript schemas for runtime validation and type inference.
