Env & Secrets Manager

Name: Env & Secrets Manager
Availability: InStock
Author: aman

Manage environment variables and secrets across development, staging, and production environments.

Updated Feb 27, 2026

Search Tags:#devops #security #secrets management #environment variables #credential rotation #git security

Ready to run

npx skills add https://github.com/amanhsn/flyerbuild --skill env-secrets-manager-amanhsn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Env & Secrets Manager
Source: https://github.com/amanhsn/flyerbuild/tree/main/.cursor/skills/env-secrets-manager
Command: npx skills add https://github.com/amanhsn/flyerbuild --skill env-secrets-manager-amanhsn

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 across different deployment stages, preventing leaks and ensuring consistency.

Core Features & Use Cases

.env Lifecycle Management: Automates the creation, validation, and synchronization of .env files.
Secret Leak Detection: Scans code and git history for accidentally exposed secrets.
Credential Rotation: Guides through the process of rotating compromised credentials.
Secret Manager Integrations: Connects with Vault, AWS SSM, 1Password, and Doppler.
Use Case: When onboarding a new developer, use this Skill to ensure they have the correct .env.example file and understand how to securely manage their local environment variables.

Quick Start

Use the Env & Secrets Manager skill to scan your staged git 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 prevent secrets from leaking into my git history?▼

To prevent secrets from leaking into git history, you can scan staged changes and historical commits for accidentally exposed environment variables. This detects sensitive credentials early before they are committed to the repository.

How do I automate .env file generation across development and production environments?▼

You can automate .env file generation across development, staging, and production by validating required variables and synchronizing environment configurations. This ensures consistent environment variable lifecycle management across different deployment stages.

Does this approach to secrets management integrate with HashiCorp Vault and AWS SSM?▼

Yes, this secrets management approach integrates directly with HashiCorp Vault, AWS SSM, 1Password CLI, and Doppler. This allows secure retrieval and centralized management of credentials across your deployment environments.

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

The best way to handle credential rotation is following a structured workflow that updates compromised secrets across development, staging, and production. This ensures synchronized rotation while maintaining environment consistency and application security.

Can I validate required environment variables before deploying my application?▼

Yes, you can validate required environment variables before deployment by checking local .env files against expected configurations. This prevents application startup failures caused by missing or incomplete environment variable setups.