threat_modeling

Identify security assets, trust boundaries, and STRIDE threats for a project.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/scikrikci/skills --skill threat-modeling-scikrikci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat_modeling
Source: https://github.com/scikrikci/skills/tree/main/skills/threat_modeling
Command: npx skills add https://github.com/scikrikci/skills --skill threat-modeling-scikrikci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling helps teams systematically identify assets, trust boundaries, and threats to build secure architectures from project kickoff.

Core Features & Use Cases

  • Asset enumeration: Catalogs valuable data, services, and credentials to protect.
  • Trust boundary mapping: Identifies where data and permissions cross security boundaries.
  • Threat categorization & guarantees: Applies STRIDE-inspired analysis to enumerate spoofing, tampering, information disclosure, denial of service, and privilege escalation threats, and defines required guarantees.
  • Use Case: At a new feature rollout with authentication and external integrations, generate a threat model to guide secure implementation.

Quick Start

Provide a structured threat model for a small web service by listing assets and trust boundaries, then describe one plausible STRIDE threat for each boundary.

Frequently Asked Questions about threat_modeling

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

FAQPage Schema
How do I generate a threat model for a new web service?

A threat model systematically identifies security assets, trust boundaries, and threat categories for a project. It applies a STRIDE-inspired methodology to enumerate spoofing, tampering, and information disclosure risks for secure architecture.

What is the best way to map trust boundaries during a risk assessment?

Mapping trust boundaries during a risk assessment involves identifying where data and permissions cross security boundaries. The threat modeling process catalogs these transitions to define required guarantees and isolate potential spoofing or tampering threats.

How do I use STRIDE analysis to categorize security threats?

STRIDE analysis categorizes security threats by assessing spoofing, tampering, information disclosure, denial of service, and elevation of privilege risks. The threat model applies this methodology across identified assets and boundaries to define required security guarantees.

Can I create a threat model for external integrations and authentication flows?

Yes, threat modeling supports new feature rollouts with authentication and external integrations. It catalogs valuable data and credentials, maps trust boundaries, and enumerates STRIDE threats to guide secure implementation.

What is included in a structured threat model document?

A structured threat model document summarizes identified security assets, mapped trust boundaries, enumerated STRIDE threats, and required security guarantees. It provides a comprehensive overview of spoofing, tampering, information disclosure, and privilege escalation risks.

Do I need prior security architecture experience to enumerate assets and boundaries?

No prior security architecture experience is required to enumerate assets and boundaries. The threat modeling process uses a lightweight STRIDE-inspired methodology to systematically identify valuable data, map trust boundaries, and assess threat categories for your project.