Environment and secrets management lifecycle: .env scaffolding, validation, leak detection, and rotation across Vault, AWS SSM, 1Password, and Doppler.
SkillScore55Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/20/2026
What it changes
Passed 12 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill55%
Checks it passed that the model alone missed
Uses env_sync_checker.py with .env.* files against the .env.example baseline.
Specifies blocking the commit transaction if any matching secret patterns are detected.
Recommends running secret_scanner.py across git commit history and the entire working tree.
and 3 more in the full report
6 fixed6 passed either way9 still failing1 broke
Pass-rate lift
+23 pp
Tokens
+66%
Agent turns
0%
Response time
-1%
Model gemini-3.6-flashMeasured 8/20/2026v112 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Before revoking a compromised OAuth client secret that has been leaked, what is the first step in the 4-step credential rotation playbook before generating a replacement key?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies scope analysis as the first step to discover all services, cron jobs, and background workers utilizing the secret.
Missed
Passed
Emphasizes mapping all dependent systems to prevent accidental outage during rotation.
Passed
Passed
case-20 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md72 lines8 filesincludes scripts
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.
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
Tool
Purpose
Command
env_validator.py
Validate a .env against .env.example: missing/extra vars, empty secrets, leaked credentials