Secrets management
Skill kimtth/agent-skill-100-lines-or-less/skills/secrets-management
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill secrets-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: handle credentials, keys, and tokens without leaking them into code, logs, or history.
SKILL.md
1.1 KB, as published. Nobody here has run it
Goal: keep secrets out of source and accessible only to what needs them.
Use for:
- storing API keys, passwords, and certificates
- wiring secrets into apps and CI safely
- responding to a leaked credential
Workflow:
- Keep secrets out of source control entirely.
- Load them from environment or a secrets manager at runtime.
- Scope each secret to least privilege.
- Rotate secrets regularly and on any suspicion of leak.
- Keep secrets out of logs, errors, and crash dumps.
- Scan the repo and history for accidental commits.
Practices:
- a secrets manager or vault over plaintext files
- per-environment secrets, never shared across stages
- short-lived credentials where supported
- pre-commit secret scanning
Rules:
- never commit a secret; if you do, rotate it immediately
- never log or echo secret values
- grant least privilege and rotate on a schedule
- do not pass secrets on the command line where they leak to history