create-threat-model

Generate STRIDE threat models with trust boundaries and prioritized mitigations.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-threat-model-jerelvelarde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-threat-model
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-threat-model
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-threat-model-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates STRIDE threat modeling to identify security risks and attack vectors in a system or component.

Core Features & Use Cases

  • Identify trust boundaries across client/server, service/service, and admin interfaces.
  • Apply STRIDE at each boundary to enumerate threats and map them to mitigations.
  • Produce a prioritized threat model document with recommended mitigations and write it to the engineering docs.

Quick Start

Threat-model the specified system by identifying trust boundaries, applying STRIDE, and detailing mitigations.

Frequently Asked Questions about create-threat-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a STRIDE threat model for my software architecture?

STRIDE threat modeling identifies security risks by analyzing threats across trust boundaries like client/server and service/service interfaces. It applies Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege categories to enumerate attack vectors and map mitigations.

Can I use STRIDE threat modeling for design reviews and risk remediation planning?

STRIDE threat modeling prioritizes mitigations by applying threat categories at each identified trust boundary within the system architecture. This process maps enumerated threats directly to recommended mitigations and writes the prioritized results into your engineering documentation.

What's the best way to identify trust boundaries for a security risk assessment?

To automate STRIDE threat modeling, provide engineering and product documents that describe the software feature architecture. The system parses this context to identify trust boundaries and apply STRIDE categories, producing a documented threat-model file automatically.

Do I need architecture documents to perform an automated threat assessment?

After completing a STRIDE threat model, you get a prioritized threat model document with recommended mitigations written directly to your engineering docs. This output supports downstream security assessments and risk remediation planning for the reviewed software features.