CtrlK
BlogDocsLog inGet started
Tessl Logo

stride-analysis-patterns

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

The canonical home for this skill is stride-analysis-patterns in popey/claude-code-skills

SKILL.md
Quality
Evals
Security

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.
Repository
popey/claude-code-skills
Last updated
First committed

Canonical home

popey/claude-code-skills
In sync

since Sep 26, 2026

Also appears in

popey/claude-code-skills
In sync

since Sep 26, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.