Env & Secrets Manager

Manage environment variables and secrets across application lifecycles.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Tonybleything76/more-claude-skills --skill env-secrets-manager-tonybleything76
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Env & Secrets Manager
Source: https://github.com/Tonybleything76/more-claude-skills/tree/main/engineering/env-secrets-manager
Command: npx skills add https://github.com/Tonybleything76/more-claude-skills --skill env-secrets-manager-tonybleything76

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive solution for managing environment variables and sensitive secrets throughout the application lifecycle, preventing leaks and ensuring consistency across development, staging, and production environments.

Core Features & Use Cases

  • Automated .env.example generation: Strips values from .env files to create a template for required variables.
  • Required variable validation: Ensures all necessary environment variables are set before application startup or deployment.
  • Secret leak detection: Scans Git history and working tree for accidentally committed secrets.
  • Credential rotation workflow: Guides through the process of rotating compromised credentials.
  • Secret manager integrations: Supports HashiCorp Vault, AWS SSM, 1Password CLI, and Doppler.
  • Use Case: When onboarding a new developer, use this skill to generate the .env.example file and then validate that all required variables are set in their local .env file before they can run the application.

Quick Start

Generate the .env.example file from your current .env file.

Frequently Asked Questions about Env & Secrets Manager

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

FAQPage Schema
How do I prevent accidentally committed secrets in my Git history?

Secret leak detection scans your Git history and working tree to find accidentally committed secrets, preventing sensitive data exposure across development and production environments.

How do I generate a .env.example file from my current environment variables?

Automated .env.example generation strips values from your .env files to create a template, ensuring new developers know exactly which required environment variables need configuration.

Can I use this to validate required environment variables before application startup?

Required variable validation ensures all necessary environment variables are set before application startup or deployment, preventing runtime failures caused by missing credentials.

Does this work with HashiCorp Vault and AWS SSM for secrets management?

Secret manager integrations support HashiCorp Vault, AWS SSM, 1Password CLI, and Doppler to ensure secure credential handling and synchronization across your environments.

What is the best way to rotate compromised credentials in production?

A credential rotation workflow guides you step-by-step through the process of rotating compromised credentials, ensuring secure updates across integrated secret managers.