Stats
Actions
Tags
From kdoc
Create a STRIDE threat model by reading the threat-model template and schema, then writing the result under Knowledge/ThreatModels. Use when the user asks for a threat model or says threat model for a module or feature.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kdoc:create-threat-modelThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to create threat models with file tools only.
Use this skill to create threat models with file tools only.
core/templates/threat-model.md.core/schema/frontmatter-schemas.json and use the threat-model definition as the validation contract.Knowledge/ThreatModels/{module-name}.md.threat-model frontmatter fields.Knowledge/ThreatModels/.kdoc_validate. The skill must still work without MCP.kdoc:governance-checkkdoc:create-guideAfter creating the threat model:
~/.ai-sessions/spool/ exists.kdoc.artifact_created event to ~/.ai-sessions/spool/events.jsonl.event_data.path and threat-model in event_data.type.Example:
echo '{"event_type":"kdoc.artifact_created","event_data":{"type":"threat-model","path":"Knowledge/ThreatModels/auth.md"},"source":"skill:kdoc","created_at":"2026-03-24T12:00:00.000Z"}' >> ~/.ai-sessions/spool/events.jsonl
npx claudepluginhub mariogusmao/mg-plugins --plugin kdocWalks STRIDE threat modeling before writing auth, secrets, OAuth, external API, file upload, deserialization, or exec code. Helps prevent security bugs at the design stage.
Generates structured STRIDE threat models for features/modules. Maps attack surfaces using shieldkit_surface, identifies threats/actors, assesses risks, suggests mitigations.
Systematically identify and document threats using the STRIDE framework (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege). Use when designing systems, reviewing architectures, conducting security design reviews, or updating threat models.