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
Threat-model a design with STRIDE: draw the data-flow diagram and trust boundaries, walk STRIDE per element, rank threats by likelihood×impact, and map each to a mitigation or a routed accepted-risk.
How this skill is triggered — by the user, by Claude, or both
Slash command
/security-engineering:threat-modeling-strideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** find design flaws before they ship.
Purpose: find design flaws before they ship.
Processes, data stores, external entities, data flows — and the trust boundaries they cross.
| Threat | Property violated |
|---|---|
| Spoofing | Authentication |
| Tampering | Integrity |
| Repudiation | Non-repudiation |
| Info disclosure | Confidentiality |
| Denial of service | Availability |
| Elevation of privilege | Authorization |
Likelihood × impact. Each credible threat -> mitigate / transfer / accept. Acceptance routes to security-reviewer. Threats cluster where sensitive data flows.
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.