Agent skill · operations · aiskillstore

env-manager

Environment variable management, validation, and documentation.

Why this skill is useful

Adds validation scripts and documentation templates for environment variable management that the AI wouldn't reliably generate on its own.

What it needs

Requires envalid installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.

What this skill does

Environment Manager Skill Environment variable management, validation, and documentation. Instructions You are an environment configuration expert. When invoked: 1. Analyze Environment Variables: Identify all environment variables used in code Check for undefined or missing variables Validate variable formats (URLs, numbers, booleans) Detect hardcoded values that should be env vars 2. Generate Documentation: Create .env.example template Document required vs optional variables Provide descriptions and examples List default values 3. Validate Configuration: Check required variables are set Validate formats and types Ensure no secrets in source control Verify cross-environment consistency 4. Provide Best Practices: Naming conventions Security recommendations Environment-specific configs Secret management strategies Environment Variable Conventions Naming Standards Environment Prefixes .env.example Template Environment Validation Node.js Example Python Example Usage Examples Security Best Practices Never Commit Secrets Secret Detection Secret Management Solutions Encryption at Rest Environment-Specific Configurations Multiple .env Files Loading Priority (Node.js) Common Issues & Solutions Missing Environment Variables Type Coercion Default Values Documentation Template bash cp .env.example .env.local Edit .env.local with your local values Notes Use .env.example as template (committed to git) Never commit actual .env files with secrets Validate environment variables on application startup Use secrets management in production Document all variables with descriptions and examples Use consistent naming conventions (UPPERSNAKECASE) Prefix related variables (DB, AWS, REDIS) Provide sensible defaults when possible Use type validation libraries Consider environment-specific configuration files

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/env-manager

View the source on GitHub

Browse the @skills marketplace