env-manager

Validate, synchronize, and secure environment variables across deployment platforms.

146|31|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm --skill env-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-manager
Source: https://github.com/bobmatnyc/claude-mpm/tree/main/src/claude_mpm/skills/bundled/infrastructure/env-manager
Command: npx skills add https://github.com/bobmatnyc/claude-mpm --skill env-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Systematic validation, security scanning, synchronization, and documentation generation for environment variables across development and deployment platforms.

Core Features & Use Cases

  • Validation of env files and framework-specific checks
  • Security scanning for exposed credentials
  • Synchronization with deployment platforms and secret managers
  • Framework-aware patterns and troubleshooting

Quick Start

  1. Validate local .env structure
  2. Compare with .env.example
  3. Check framework-specific rules (Next.js, Express, etc.)

Frequently Asked Questions about env-manager

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

FAQPage Schema
How do I validate environment variables across development and deployment platforms?

Environment variable validation checks .env files for completeness, framework-specific rules, and security issues before deployment. This Skill automates validation across local development, CI/CD pipelines, and platforms like Vercel, Railway, and Heroku, catching missing or misconfigured variables before they cause failures.

Can I detect exposed credentials and secrets in my environment files?

Security scanning identifies credential patterns and exposed secrets in environment variables. This Skill detects common secret formats, prevents accidental exposure, and applies zero-log policies to ensure sensitive data isn't logged during validation or synchronization.

How do I synchronize environment variables with deployment platforms?

Environment synchronization compares local .env files with deployment platform configurations and updates them safely. This Skill supports dry-run validation, JSON output for automation, and safe synchronization across Next.js, Vercel, Railway, Heroku, and other frameworks without manual platform access.

What's the best way to document required environment variables for my team?

.env.example generation creates a template documenting all required variables without exposing secrets. This Skill auto-generates frameworks-specific examples from your configuration, ensuring new team members know exactly which variables to configure locally.

Does this work with framework-specific environment requirements like Next.js?

Framework-aware validation checks environment variables against Next.js, Express, and other framework-specific rules. This Skill recognizes framework patterns, applies appropriate validation rules, and troubleshoots framework-specific configuration issues.

Can I integrate environment validation into my CI/CD pipeline?

CI/CD integration validates environment variables automatically during pipeline execution without external dependencies. This Skill runs pure Python with JSON output, enabling seamless integration into GitHub Actions, GitLab CI, and other CI/CD systems for pre-deployment checks.