secrets-management · sickn33 — Claude Code skill: what it does, how to install
secrets-management — a skill that walks an agent through secret handling in CI/CD: picking a backend, scoping access, rotating credentials and proving values never reach logs or artifacts.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a claude-codeWhat secrets-management does
The skill turns a vague request to keep secrets safe into a sequence. It starts by asking which secrets exist, who owns them and which processes read them, then picks a backend already in the stack: Vault, a cloud secret manager or the protected store on the host. Environment boundaries and least privilege get written down rather than assumed. Vault and GitHub Actions each have a companion file inside the skill, references/vault-setup.md and references/github-secrets.md, and dev mode with root tokens is treated as unfit for production.
Where the backend allows it, retrieval moves to short-lived workload identity. Before switching that on, the agent checks issuer, audience and workload restrictions, and confirms a denied request actually fails. Rotation runs in four stages: prepare, switch the consumer, verify, revoke the old credential. Retries are the trap — they must not leave the database and the secret store holding different passwords.
Masking does not make logging secrets safe. A value that reached output gets revoked or rotated; deleting the log line is not enough. Secrets also linger in infrastructure state, subprocess environments and backups, so those boundaries need a look. The skill expects an authorized system: it will not touch live credentials or deploy secret infrastructure on its own. Verification runs on synthetic markers through logs, error paths, artifacts and crash reports.
What it helps with
- pick a secret backend that matches the existing stack
- split access between environments and individual jobs
- move credential issuing to short-lived workload identity
- run a rotation that leaves no split credentials behind
- prove logs and artifacts contain no secret values
Example prompts for the agent
- Trace how the deploy job gets its database password and give that retrieval to the trusted job only.
- Check the pipeline for secrets leaking into logs or build artifacts, then propose a rotation plan.
- Set up Vault retrieval for CI without a root token or dev mode.
How to install secrets-management
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a claude-code2Manually: put the files in place
~/.claude/skills/secrets-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/secrets-management/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a codex2Manually: put the files in place
.agents/skills/secrets-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a cursor2Manually: put the files in place
.cursor/skills/secrets-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/secrets-management2Manually: put the files in place
.github/skills/secrets-management/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/secrets-managementManually: put the files in place
.devin/skills/secrets-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about secrets-management
How do I install secrets-management in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill secrets-management -a claude-code. The skill file lands at ~/.claude/skills/secrets-management/SKILL.md.
What does secrets-management do?
It works through how a pipeline obtains secrets: backend choice, access policy, short-lived identity and rotation. It also checks that values stay out of logs, artifacts and error reports.
Is masking enough to keep secrets out of logs?
No. Once a value has reached output, revoke or rotate it. Removing the log entry alone leaves the credential live.
Source text
SKILL.md · MIT
--- name: secrets-management description: "Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools." risk: critical source: community date_added: "2026-02-27" --- # Secrets Management ## When to Use Design or repair secret retrieval, CI credentials, workload identity, access policies and rotation for an authorized system. ## Inputs Identify secret names and owners, consumers, environments, authentication mechanism and the rotation/recovery policy. Inspect configuration without displaying values. ## Procedure 1. Choose the existing supported backend: Vault, a cloud secret manager or the host's protected secret store. Keep environment boundaries and minimum privileges explicit. 2. For Vault, read `references/vault-setup.md`. Development mode and root tokens are not production configuration. 3. For GitHub Actions, read `references/github-secrets.md`. Keep pull-request validation separate from privileged jobs. Supply values to the consuming process, never interpolate them into generated shell source or print them for debugging. 4. Prefer short-lived workload identity when the backend supports it. Check issuer, audience, workload/environment restrictions and denied access before enabling retrieval. 5. Rotate through prepare, consumer switch, verification and old-credential revocation. Use the backend's supported rotation protocol; retries must not leave the database and secret store on different credentials. 6. Inspect logs, error paths, artifacts and crash reports with synthetic secret markers. Record metadata such as operation, principal and outcome rather than values. ## Example A deployment needs a database credential. The trusted job retrieves it through the configured identity and passes it only to the migration process. Test missing access and an expired identity in staging. Verify no credential appears in output, and that a failed rotation leaves a recoverable working state. ## Verification - Authorized retrieval succeeds; a different workload or environment is denied. - Missing credentials fail closed without exposing values. - Rotation and rollback are exercised with synthetic data. - Logs and artifacts contain no secret markers, including on failure. - Exposed credentials are revoked or rotated; merely deleting their log entry is insufficient. ## Limitations Masking cannot make logging secrets safe. Secret data can persist in infrastructure state, subprocess environments or backups; review those boundaries explicitly. Do not alter real credentials or deploy secret infrastructure without authorization. ## Sources - [GitHub secure workflow guidance](https://docs.github.com/en/actions/reference/security/secure-use) - [Vault production hardening](https://developer.hashicorp.com/vault/docs/concepts/production-hardening)
© sickn33 · MIT · sickn33/agentic-awesome-skills
Similar skills
All skills for Security →secrets-management by other authors comes first.