Env & Secrets Manager

Manage .env files, validate variables, and detect secret leaks in git history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire lifecycle of environment variables and sensitive secrets, preventing leaks and ensuring consistency across development and production environments.

Core Features & Use Cases

  • .env Management: Automates the creation, validation, and syncing of .env files and their examples.
  • Secret Leak Detection: Scans code and git history for accidentally exposed credentials.
  • Credential Rotation: Provides playbooks for rotating compromised secrets across various platforms.
  • Use Case: Before committing code, run the secret scan to ensure no API keys are accidentally included, preventing costly breaches.

Quick Start

Run the script to scan staged changes for any accidentally committed secrets.

Frequently Asked Questions about Env & Secrets Manager

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

FAQPage Schema
How do I scan git history for accidentally committed secrets and environment variables?

To detect secret leaks in git history, you can scan staged changes and past commits for exposed credentials. This prevents accidentally committed API keys from causing costly security breaches before pushing code.

How do I automate .env file management and generate .env.example files?

Automating .env file management involves creating, validating, and syncing environment variables alongside auto-generated .env.example files. This ensures configuration consistency across development, staging, and production environments.

Does this secrets management workflow integrate with HashiCorp Vault and AWS SSM?

Yes, this secrets management workflow integrates directly with HashiCorp Vault, AWS SSM, 1Password CLI, and Doppler. It securely handles credentials and environment variables across multiple deployment environments.

What is the best way to handle credential rotation for compromised environment secrets?

Handling credential rotation requires following structured playbooks to update compromised secrets across platforms. This ensures secure, systematic rotation of environment variables without disrupting application availability.

How do I validate required environment variables before deploying to staging or production?

Validating required environment variables involves checking that all mandatory secrets are present and correctly formatted before deployment. This prevents runtime failures and configuration drift across staging and production environments.

Why do I need secret leak detection in my CI/CD pipeline?

Secret leak detection in your CI/CD pipeline identifies accidentally exposed credentials in code and git history before deployment. Scanning staged changes proactively prevents sensitive environment variables from reaching public repositories.