agentsclimarketplace
Sign in

Secrets management

Skill shinzoxD/knackbox/skills/coding/secrets-management

Handle secrets safely in apps and infrastructure without committing credentials. Use whenever the user asks about API keys, secret managers, .env handling, rotation, CI secrets, or how to inject credentials at runtime.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill secrets-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 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 file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 323 tokens by cl100k_base, as published. Nobody here has run it

Secrets Management

Secrets are credentials that grant power. Minimize sprawl, never commit them, prefer short-lived credentials, and plan rotation.

Principles

  1. No secrets in git, logs, client bundles, or screenshots.
  2. Inject at runtime from a secret manager or sealed CI store.
  3. Least privilege and per-environment secrets.
  4. Rotation and revocation paths tested.
  5. Prefer OIDC/workload identity over long-lived static keys when possible.

Workflow

  1. Inventory secret types (DB, API, TLS, signing).
  2. Choose storage (cloud SM, k8s secrets + encryption, CI OIDC).
  3. Access patterns for apps, humans, and automation.
  4. Local dev: .env gitignored + sample .env.example without values.
  5. Leak response: rotate, audit logs, invalidate.

Output format

## Secrets plan

### Inventory
…

### Storage & injection
…

### CI/CD
…

### Rotation
…

### Anti-patterns to remove
…

Rules

  1. Never ask the user to paste live production secrets into chat if avoidable; use placeholders.
  2. Distinguish public client IDs from private client secrets.
  3. Encrypt-at-rest is not enough if authz is wide open.
  4. Document break-glass carefully.
  5. Redact in examples always.

Edge cases

  • Mobile apps: no long-lived master secrets in binaries.
  • Webhooks: signing secrets rotation dual-key window.
  • Multi-tenant: per-tenant secret isolation.

What ships with it: 1 file

1.2 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.