env-audit

Audits environment variable management across eight dimensions including secret exposure and startup validation.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill env-audit-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-audit
Source: https://github.com/greglas75/zuvo/tree/main/skills/env-audit
Command: npx skills add https://github.com/greglas75/zuvo --skill env-audit-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Environment variables are often undocumented, unvalidated, or accidentally committed to repositories, causing production crashes, leaked secrets, and painful onboarding. This Skill audits your entire env var setup and produces a scored report with prioritized fixes. ## Core Features & Use Cases - Eight-dimension audit (ENV1-ENV8): Checks variable completeness, unused vars, startup validation, secret exposure, environment parity, type safety, default values, and documentation, with critical gates that fail the audit on committed secrets or missing validation. - Multi-stack detection: Recognizes Node.js (process.env), Python (os.environ), Vite (import.meta.env), Next.js (NEXT_PUBLIC_), Cloudflare Workers, and Docker Compose patterns automatically. - Scored report with remediation roadmap: Outputs a 0-100 score, a variable coverage matrix, severity-sorted findings with file:line citations, and quick-win to medium-term fix plans. - Use Case: Before a production deploy, run the audit to catch a hardcoded API key in a NEXT_PUBLIC_ variable and a missing .env.example, then follow the remediation roadmap to add Zod schema validation at startup. ## Quick Start Run the env-audit skill on my project to check for exposed secrets, missing validation, and undocumented environment variables.

Frequently Asked Questions about env-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit environment variables in a Node.js project?

Run the env-audit skill against your project root. It scans process.env usage, compares variables against .env.example, checks for startup validation libraries like Zod or envalid, and reports a score with severity-ranked findings.

How to check if secrets are committed to a git repository?

The audit's ENV4 dimension checks .gitignore coverage, runs git ls-files for committed .env files, searches for hardcoded API keys and tokens, and flags NEXT_PUBLIC_ or VITE_ variables containing secrets. Any committed secret triggers a critical gate failure.

Does the env audit support Python and Next.js projects?

Yes. It auto-detects the stack from files like requirements.txt, pyproject.toml, next.config, and vite.config, then searches the matching access patterns such as os.environ, os.getenv, import.meta.env, and NEXT_PUBLIC_ variables.

Can I audit only secret exposure without the full report?

Yes. Pass the --secrets-only flag to run only the ENV4 secret exposure dimension, or use --parity to run only ENV5 environment parity. You can also scope the audit to a subdirectory for monorepo packages.

When should I not use an environment variable audit?

Do not use it for general source-code secret scanning (use a security audit instead), CI pipeline configuration review, or infrastructure auditing. It focuses specifically on env var definition, usage, validation, and documentation.