From security-engineering
Manage secrets safely: detect them in code/config/logs, vault them, federate with short-lived credentials, rotate on a schedule, and treat any committed secret as compromised (rotate, don't just delete).
How this skill is triggered — by the user, by Claude, or both
Slash command
/security-engineering:secrets-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** keep secrets out of code and short-lived.
Purpose: keep secrets out of code and short-lived.
Secret scanning in CI + pre-commit. Scan code, config, and logs.
On a schedule and on personnel change. A committed secret is compromised — rotate it, deleting the commit is not enough (it's in history + clones).
npx claudepluginhub mcorbett51090/ravenclaude --plugin security-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.