Stride Analysis Patterns

This is a straightforward implementation of STRIDE threat modeling for Claude. It walks you through identifying Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege threats in your systems. Best used when you're actually doing threat modeling work, reviewing architecture decisions, or prepping for security audits. The skill includes an implementation playbook with detailed patterns and examples, which is genuinely helpful since STRIDE can feel abstract without concrete scenarios. It's solid for teams that want structured security analysis but don't want to reinvent the methodology themselves. Just remember it's a framework guide, not a replacement for actually validating threats in your specific environment.

skills.sh installs: 199
GitHub stars: 39.4K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill stride-analysis-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

STRIDE Analysis Patterns

Systematic threat identification using the STRIDE methodology.

Use this skill when

Starting new threat modeling sessions
Analyzing existing system architecture
Reviewing security design decisions
Creating threat documentation
Training teams on threat identification
Compliance and audit preparation

Do not use this skill when

The task is unrelated to stride analysis patterns
You need a different domain or tool outside this scope

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.

Resources

resources/implementation-playbook.md for detailed patterns and examples.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.