env-validator

Validate .env file existence and content parity with code usage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BruceTyndall/socelle-global --skill env-validator-brucetyndall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-validator
Source: https://github.com/BruceTyndall/socelle-global/tree/main/.agents/skills/env-validator
Command: npx skills add https://github.com/BruceTyndall/socelle-global --skill env-validator-brucetyndall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common issue of inconsistent and insecure environment variable management across different applications and runtime environments, preventing configuration drift and potential security vulnerabilities.

Core Features & Use Cases

  • Environment File Auditing: Checks for the presence and content of .env files (.env, .env.local, .env.example, etc.).
  • Required Variable Verification: Ensures critical environment variables are declared in .env files.
  • Code-vs-Declaration Parity: Identifies environment variables used in code but not declared in configuration files.
  • Hardcoded Value Detection: Scans code for hardcoded sensitive values that should be managed via environment variables.
  • Use Case: Before deploying a new feature, run this skill to confirm that all necessary API keys and configuration settings are correctly defined and that no sensitive information is accidentally hardcoded in the codebase.

Quick Start

Run the env-validator skill to check the environment variable configuration for the SOCELLE-WEB application.

Frequently Asked Questions about env-validator

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

FAQPage Schema
How do I check for missing environment variables in my codebase?▼

To check for missing environment variables, you can audit your `.env` files against code usage to detect variables used in code but not declared in configuration files. This prevents missing configuration values during application runtime.

What is environment variable configuration parity and why does it matter?▼

Environment variable configuration parity ensures that variables used in code match those declared in `.env` files. Maintaining this parity prevents configuration drift and avoids potential security vulnerabilities across different runtime environments.

How do I detect hardcoded sensitive values in source code?▼

To detect hardcoded sensitive values, scan your codebase for secrets and configuration settings that should be managed via environment variables. This identifies unprotected sensitive information accidentally left in the source code.

Do I need dependencies installed to audit .env files?▼

Yes, you need a checked-out codebase with dependencies installed to audit `.env` files. This allows the validation process to accurately verify required variables and check code-vs-declaration parity.

What's the best way to prevent configuration drift across runtime environments?▼

The best way to prevent configuration drift is to validate environment variable configuration by checking `.env` file existence and content parity with code usage. This ensures critical variables are declared and undeclared variables are flagged.