env-audit

Compare .env against .env.example to identify missing or empty environment variables.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate the completeness and correctness of their environment configuration by comparing the active .env file with the reference .env.example, identifying missing or empty variables and preventing secrets leakage.

Core Features & Use Cases

  • Compare .env and .env.example to surface missing or empty variables.
  • Highlight critical variables and provide guidance on their purpose and correct values.
  • Security-focused checks to detect secrets accidentally committed or exposed in code, and to support onboarding and developer setup.

Quick Start

Run the audit to compare .env against .env.example and generate a report outlining missing variables, empty values, and potential secret exposures.

Frequently Asked Questions about env-audit

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

FAQPage Schema
How do I check for missing environment variables between .env and .env.example?

To check for missing environment variables, compare your active .env file against the reference .env.example to surface missing keys, validate non-empty values, and generate a remediation report.

How do I detect exposed secrets in my Python or FastAPI project configuration?

Detect exposed secrets by running a security-focused audit on your environment configuration to flag accidentally committed or exposed secrets in your Python/FastAPI project code.

Does environment config auditing work for CI pipelines and local development?

Environment config auditing applies to both CI pipelines and local development, ensuring critical keys are present and validating non-empty values across your project setup.

What is the best way to validate non-empty values for critical environment variables?

The best way to validate non-empty values is to audit the environment configuration, highlighting critical variables and providing guidance on their purpose and correct required values.