What problem does it solve? Credentials end up committed to git, baked into Docker images, or shared as one org-wide key, turning a single leak into a multi-team crisis. This Skill provides a systematic workflow for deciding where secrets live, how they reach runtime, and how to rotate them routinely. ## Core Features & Use Cases - Identity-first design: Replace stored credentials with workload identity, OIDC federation for CI-to-cloud auth, and managed identities wherever the platform supports it. - Tiered storage and delivery: Choose the right store per environment (secrets manager for production, CI secret stores for pipelines, gitignored .env for local dev) and inject secrets at runtime without persisting them in images, configs, or logs. - Rotation and leak prevention: Implement two-key overlap rotation, per-service scoping, gitleaks/trufflehog scanning, push protection, and audit-log monitoring. - Use Case: Auditing a payments service, you find AWS keys in GitHub repo secrets, a DB password in git history, and a Stripe key in a Docker layer. The workflow guides you to OIDC federation, a secrets manager with per-env values, runtime injection, and a practiced 15-minute rotation runbook. ## Quick Start Audit how my application currently gets its secrets and propose a storage, rotation, and scanning setup following the secrets-management workflow.