Agent skill

Env Secrets Manager

by borghei in borghei/Claude-Skills

Environment and secrets management lifecycle: .env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler.

MITAuto-check: notesDevOps & Cloud

Install Env Secrets Manager

skills CLI
$ npx skills add borghei/Claude-Skills --skill env-secrets-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills env-secrets-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/env-secrets-manager .claude/skills/env-secrets-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
env-secrets-manager
GitHub stars
874
Token cost
~1.6k tokens
SKILL.md length
659 words
Files
8 (incl. scripts, references)
Skills in repo
364
Repo updated
First seen
Licence
MIT

At a glance

Environment and secrets management lifecycle: .env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler.

  • Setting up projects
  • SKILL.md covers Core Capabilities, When to Use, Clarify First and Tools, plus 3 more sections
  • Runs Python scripts from its folder; calls python
  • Scanning for leaked secrets

What it does

Env Secrets Manager is an agent skill from borghei/Claude-Skills. Environment and secrets management lifecycle: .env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler. Use when setting up projects, scanning for leaked secrets, or rotating credentials.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/best-practices-and-troubleshooting.md`, `references/env-file-structure.md` and `references/leak-detection-and-rotation.md`).

It sits in DevOps & Cloud, covering Secrets management. It works with Amazon Web Services. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Setting up projects
  • Scanning for leaked secrets
  • Rotating credentials

Example prompts

  • “/env-secrets-manager”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Env Secrets Manager loads about 1.6k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 659 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:4
    onment and secrets management lifecycle: .env scaffolding, validation, leak detection,
  • NoteMentions a .env fileSKILL.md:19
    riable and secrets management lifecycle: .env file structure across dev/staging/production, .env.example auto-generation
  • NoteMentions a .env fileSKILL.md:42
    - [ ] **Task** — scaffold/validate a `.env`, scan for leaked secrets, or check env drift (selects `env_validator.py` vs
  • NoteMentions a .env fileSKILL.md:43
    - [ ] **Target paths** — the `.env`/`.env.example` files or directory to scan (the input the tools read)
  • NoteMentions a .env fileSKILL.md:52
    | `env_validator.py` | Validate a `.env` against `.env.example`: missing/extra vars, empty secrets, leaked credentials |
  • NoteMentions a .env fileSKILL.md:54
    ft | `python scripts/env_sync_checker.py .env.* --baseline .env.example` |
  • NoteMentions a .env fileSKILL.md:60
    es/env-file-structure.md)** — canonical `.env` layout, the `.env.*` file hierarchy, required `.gitignore` patterns, and
  • NoteMentions a .env fileSKILL.md:68
    - `.env` file scaffolding, hierarchy, and validation for any language/framework
  • NoteMentions a .env fileSKILL.md:86
    ists | Onboarding workflow consumes the `.env` hierarchy and validation script |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 659 words, ~1,648 tokens.

Download SKILL.mdSave it as .claude/skills/env-secrets-manager/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
env-secrets-manager
description
Environment and secrets management lifecycle: .env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler. Use when setting up projects, scanning for leaked secrets, or rotating credentials.
license
MIT + Commons Clause
metadata.version
1.1.0
metadata.author
borghei
metadata.category
engineering
metadata.domain
security-devops
metadata.tier
POWERFUL
metadata.updated
2026-06-17
metadata.frameworks
vault, aws-ssm, 1password-cli, doppler

Env & Secrets Manager

Complete environment variable and secrets management lifecycle: .env file structure across dev/staging/production, .env.example auto-generation that strips sensitive values, required-variable validation at startup, secret leak detection in git history, credential rotation playbooks, environment drift detection, and integration with HashiCorp Vault, AWS SSM, 1Password CLI, and Doppler.

Core Capabilities

  • .env lifecycle — structured layout with categorized sections, auto-generated .env.example (strips secrets), environment-specific files, and fail-fast startup validation.
  • Secret leak detection — regex scan of git history, working tree, and staged files; pre-commit hooks; patterns for API keys, tokens, passwords, private keys.
  • Credential rotation — per-secret playbooks, scope analysis, zero-downtime dual-read rotation, post-rotation verification and monitoring.
  • Secret manager integration — HashiCorp Vault (KV v2 + OIDC), AWS SSM Parameter Store (KMS), 1Password CLI (template injection), Doppler (project/config).
  • Drift detection — compare variable key sets between staging and production and report missing/extra keys.

When to Use

  • Setting up a new project — scaffold .env.example and validation.
  • Before every commit — scan for accidentally staged secrets.
  • Post-incident — rotate leaked credentials systematically.
  • Onboarding developers — provide complete environment setup.
  • Auditing — detect environment drift between staging and production.
  • Compliance — demonstrate secret management practices.

Clarify First

Before running, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Task — scaffold/validate a .env, scan for leaked secrets, or check env drift (selects env_validator.py vs secret_scanner.py vs env_sync_checker.py)
  • Target paths — the .env/.env.example files or directory to scan (the input the tools read)
  • Secret manager — Vault, AWS SSM, 1Password, or Doppler (determines the integration and rotation commands generated)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

ToolPurposeCommand
env_validator.pyValidate a .env against .env.example: missing/extra vars, empty secrets, leaked credentialspython scripts/env_validator.py .env.example .env --strict --check-secrets
secret_scanner.pyScan a directory/file for hardcoded secrets via pattern matchingpython scripts/secret_scanner.py ./src --severity high --json
env_sync_checker.pyCompare env configs across dev/staging/prod and report driftpython scripts/env_sync_checker.py .env.* --baseline .env.example

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/env-file-structure.md — canonical .env layout, the .env.* file hierarchy, required .gitignore patterns, and the full Python startup-validation script. Read when scaffolding a project or wiring validation.
  • references/leak-detection-and-rotation.md — the git-history secret scanner, pre-commit hook, the 4-step credential rotation playbook (scope, generate, dual-write, verify), and the environment-drift detection script. Read when scanning for leaks or rotating credentials.
  • references/secret-manager-integration.md — concrete Vault, AWS SSM, and Doppler commands for storing, reading, and rotating secrets. Read when integrating a secret manager.
  • references/best-practices-and-troubleshooting.md — common pitfalls, the 8 best practices, the troubleshooting table, and the success-criteria bar. Read when reviewing a setup or debugging.
Show full SKILL.md (222 more words)Show less

Scope & Limitations

This skill covers:

  • .env file scaffolding, hierarchy, and validation for any language/framework
  • Secret leak detection in git history, staged files, and working tree
  • Credential rotation playbooks with zero-downtime dual-read strategy
  • Integration patterns for HashiCorp Vault, AWS SSM, 1Password CLI, and Doppler

This skill does NOT cover:

  • Runtime secret injection in Kubernetes (see engineering/ci-cd-pipeline-builder for deployment pipeline secrets)
  • Infrastructure-as-code for provisioning Vault clusters or SSM policies (see engineering/ci-cd-pipeline-builder)
  • Application-level encryption at rest or in transit (see engineering/api-design-reviewer for API security patterns)
  • Identity and access management (IAM) role design or SSO/OIDC provider configuration (see ra-qm-team/ compliance skills for access control frameworks)

Integration Points

SkillIntegrationData Flow
engineering/ci-cd-pipeline-builderInject secrets from Vault/SSM/Doppler into CI/CD pipeline stagesRotation playbook outputs feed pipeline secret-update steps
engineering/dependency-auditorFlag dependencies that bundle or require hardcoded credentialsDependency audit findings trigger secret leak scans on affected repos
engineering/skill-security-auditorValidate that no skill packages ship embedded secrets or credentialsSecurity audit references this skill's regex patterns for detection
engineering/codebase-onboardingInclude .env.example setup and secret-manager access in onboarding checklistsOnboarding workflow consumes the .env hierarchy and validation script
engineering/observability-designerMonitor authentication failures post-rotation; alert on anomalous secret accessPost-rotation verification metrics flow into observability dashboards
ra-qm-team/soc2-compliance-auditorDemonstrate secret management controls for SOC 2 CC6.1 and CC6.6 criteriaRotation audit logs and access policies serve as SOC 2 evidence artifacts

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references) in engineering/env-secrets-manager of borghei/Claude-Skills.

  • SKILL.md
  • references/best-practices-and-troubleshooting.md
  • references/env-file-structure.md
  • references/leak-detection-and-rotation.md
  • references/secret-manager-integration.md
  • scripts/env_sync_checker.py
  • scripts/env_validator.py
  • scripts/secret_scanner.py

Open the folder on GitHubat commit c9a1487

Compare with similar skills

Env Secrets Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Env Secrets Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Env Secrets Manager this skillborghei/Claude-Skills874—~1.6kAutomated safety check: NotesMIT
Audit Env Variablesqdhenry/Claude-Command-Suite1.3k—~2.8kAutomated safety check: NotesNone
Hashicorp VaultBagelHole/DevOps-Security-Agent-Skills1.1k—~2kAutomated safety check: PassMIT
Secrets Managementdavila7/claude-code-templates32k11 repos~2kAutomated safety check: PassMIT
Secrets Vault Manageralirezarezvani/claude-skills28k1 repos~3.6kAutomated safety check: NotesMIT
Detecting Compromised Cloud Credentialsmukul975/Anthropic-Cybersecurity-Skills34k—~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Audit Env Variables

    qdhenry/Claude-Command-Suite

    Analyze environment variables in JavaScript/TypeScript projects.

    1.3k GitHub stars~2.8k tokensUpdated 7 mo ago
    DevOps & CloudAuto-check: notes
  • Hashicorp Vault

    BagelHole/DevOps-Security-Agent-Skills

    Manage secrets and PKI with HashiCorp Vault. An agent skill from BagelHole/DevOps-Security-Agent-Skills.

    1.1k GitHub stars~2k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed
  • Secrets Management

    davila7/claude-code-templates

    Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools.

    32k GitHub starsUsed in 11 repos~2k tokens
    DevOps & CloudAuto-check passed
  • Secrets Vault Manager

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to set up secret management infrastructure, integrate HashiCorp Vault, configure cloud secret stores (AWS Secrets Manager, Azure Key Vault, GCP Secret…

    28k GitHub starsUsed in 1 repo~3.6k tokens
    DevOps & CloudAuto-check: notes
  • Detecting Compromised Cloud Credentials

    mukul975/Anthropic-Cybersecurity-Skills

    Detect compromised cloud credentials across AWS, Azure, and GCP by analyzing anomalous API activity, impossible-travel patterns, and credential-stuffing indicators using GuardDuty, Microsoft…

    34k GitHub stars~3.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Managing Secrets

    ancoleman/ai-design-components

    Managing secrets (API keys, database credentials, certificates) with Vault, cloud providers, and Kubernetes.

    526 GitHub stars~2.9k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check passed

More from borghei/Claude-Skills

All 364 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    874 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    874 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    874 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    874 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    874 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    874 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Env Secrets Manager

What does Env Secrets Manager do?

Environment and secrets management lifecycle: .env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler. Env Secrets Manager is an agent skill from borghei/Claude-Skills.env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler.

When should I use Env Secrets Manager?

Env Secrets Manager fits situations like: setting up projects; scanning for leaked secrets; rotating credentials.

How do I install Env Secrets Manager in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill env-secrets-manager -a claude-code`. Or copy the skill folder (engineering/env-secrets-manager in borghei/Claude-Skills) into .claude/skills/env-secrets-manager in your project. Claude Code loads it when a task matches its description.

How do I install Env Secrets Manager in Codex?

Run `npx skills add borghei/Claude-Skills --skill env-secrets-manager -a codex`. Or copy the skill folder (engineering/env-secrets-manager in borghei/Claude-Skills) into .agents/skills/env-secrets-manager in your project. Codex loads it when a task matches its description.

Can I use Env Secrets Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill env-secrets-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/env-secrets-manager, .gemini/skills/env-secrets-manager, .github/skills/env-secrets-manager and .opencode/skills/env-secrets-manager in your project.

What does Env Secrets Manager need to run?

Going by SKILL.md and its folder, Env Secrets Manager needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Env Secrets Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Env Secrets Manager safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Env Secrets Manager use?

Env Secrets Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Env Secrets Manager use?

About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Env Secrets Manager?

Skills that share tags, products or a category with Env Secrets Manager: Audit Env Variables (qdhenry/Claude-Command-Suite, 1.3k stars), Hashicorp Vault (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars), Secrets Management (davila7/claude-code-templates, 32k stars) and Secrets Vault Manager (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Env Secrets Manager?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.