Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From security-engineering
Secure the software supply chain from the consume side: ingest the SBOM, triage CVEs by reachability, pin dependencies with a deliberate update cadence, verify SLSA provenance, and defend against malicious packages.
How this skill is triggered — by the user, by Claude, or both
Slash command
/security-engineering:supply-chain-securityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** secure what the software is made of.
Purpose: secure what the software is made of.
Consume the SBOM (from devops-cicd). Include transitive deps — you can't patch what you can't see.
A vulnerable function you never call is lower priority. Reachability analysis prevents advisory-drowning.
Lockfiles + pins for reproducibility; deliberate automated-update cadence gated by tests — never blind auto-merge.
SLSA provenance verification for critical artifacts; defend against typosquat / dependency-confusion (scoped registries, scrutinize new deps + install scripts).
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.