Agent skill · software engineering · jeremylongshore
managing-environment-configurations
Implement environment and configuration management with comprehensive
Why this skill is useful
Adds automation scripts for managing environment configurations and validation that aren't commonly known.
What it needs
Requires kubectl, sops installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Managing Environment Configurations Overview Manage application configurations across development, staging, and production environments using .env files, Kubernetes ConfigMaps/Secrets, SSM Parameter Store, and cloud-native configuration services. Enforce consistency, prevent configuration drift, and implement safe promotion workflows between environments. Prerequisites Access to all target environments (dev, staging, production) Configuration management tool or pattern identified (dotenv, ConfigMaps, SSM, Consul) Version control for configuration files (separate repo or encrypted in application repo) Encryption tool for sensitive values (sops, age, sealed-secrets, or cloud KMS) Understanding of which values differ between environments vs. which are shared Instructions 1. Audit existing configuration: scan for .env files, config/ directories, Kubernetes ConfigMaps, and hardcoded values in source code 2. Classify each configuration value: public (non-sensitive, varies per env), secret (credentials, API keys), and static (same across all envs) 3. Extract hardcoded values into externalized configuration with a clear naming convention (APPDATABASEHOST, APPREDISURL) 4. Create environment-specific configuration files: .env.development, .env.staging, .env.production 5. Encrypt sensitive values using sops with cloud KMS or sealed-secrets for Kubernetes 6. Generate Kubernetes ConfigMaps and Secrets from environment files for cluster-based deployments 7. Set up configuration validation: schema checks to ensure all required variables are present before deployment 8. Implement promotion workflow: changes go to dev first, then promote to staging after testing, then to production with approval 9. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/managing-environment-configurations