CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stride-analysis-patterns

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/security-scanning/skills/stride-analysis-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well structured for progressive disclosure — a lean overview correctly deferring templates to a real, one-level-deep reference file — but the body itself offers little actionable procedure: it re-teaches the STRIDE taxonomy Claude already knows (twice) and provides no sequenced workflow for running a threat modeling session. Most of its concrete value only appears after reading references/details.md.

Suggestions

Add a numbered session workflow (e.g., 1. Define scope and draw the DFD, 2. Walk each STRIDE category using the matrix questions per element, 3. Prioritize by impact, 4. Fill in the template from references/details.md) with an explicit checkpoint to confirm all six categories were covered before prioritizing.

Replace the duplicated STRIDE enumeration (ASCII block and matrix both list the same six categories) with a single table, and cut the generic Do's/Don'ts that restate knowledge Claude already has; keep only skill-specific guidance such as how to map DFD elements to categories.

Inline one compact worked example (a single DFD element analyzed through all six categories) so the body is actionable on its own rather than deferring all concrete material to references/details.md.

DimensionReasoningScore

Conciseness

The body is short and tabular, but the Core Concepts section re-teaches textbook knowledge Claude already has — the six STRIDE categories are enumerated twice (ASCII block and threat matrix), and the Do's/Don'ts ('Be systematic', 'Involve stakeholders') are generic advice. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; not a 2 because there is no padded prose and the material is compact, not a 4 because the duplication and generic tips are genuinely removable.

3 / 5

Actionability

The threat matrix supplies concrete per-category questions ('Can attacker pretend to be someone else?', 'Can attacker modify data in transit/rest?') plus control-family mappings, which is usable heuristic guidance. But no concrete procedure for actually running an analysis is given — 'Use visual aids - DFDs help communication' and 'Prioritize realistically' are high-level hints with the specific steps deferred entirely to references/details.md. This matches 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

No sequence for conducting a threat modeling session is provided — there is no scope-definition, system-modeling (DFD), enumeration, prioritization, or documentation step, only a coverage framework (the matrix) and context triggers. 'When to Use' lists situations, not steps. This is closest to 'rough sequence present but many gaps; steps poorly defined' (the matrix implies iterating categories) rather than the fully missing/incoherent 1, and the no-validation cap does not apply since this is not a destructive or batch operation.

2 / 5

Progressive Disclosure

The body is a genuine overview and points to one real, one-level-deep bundle file with an explicit read-when signal: "Full template library lives in `references/details.md`. Read that file when you need concrete templates for this skill." references/details.md exists (26 headings of templates and worked examples) and contains no further nested references, so navigation is clear and content is appropriately split. Matches the top anchor exactly; not a 4 because there are no organization gaps to point to.

5 / 5

Total

13

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed description that clearly states what the skill does and when to use it, with natural trigger phrases in third-person voice. Its main gap is that it names only one concrete action, and 'analyzing system security' invites some overlap with general security-analysis skills.

DimensionReasoningScore

Specificity

"Apply STRIDE methodology to systematically identify threats" names the domain and one core action (systematically identify threats) but lists no further concrete actions (e.g., categorize threats, map controls, produce documentation), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. Not a 4 because it does not list several specific actions; not a 2 because the action named is concrete and domain-specific rather than generic.

3 / 5

Completeness

It explicitly answers what ("Apply STRIDE methodology to systematically identify threats") and when ("Use when analyzing system security, conducting threat modeling sessions, or creating security documentation") with concrete trigger phrases, mirroring the top anchor's exemplar structure. Not a 4 because the 'when' clause is explicit and specific with multiple natural trigger contexts rather than only weakly stated.

5 / 5

Trigger Term Quality

"Use when analyzing system security, conducting threat modeling sessions, or creating security documentation" includes natural phrases users would say ('threat modeling', 'system security', 'security documentation'). Missing common variations such as 'threat model', 'security review', or 'security audit', so it does not reach the comprehensive synonym coverage of a 5 but sits clearly above 'some relevant keywords' (3).

4 / 5

Distinctiveness Conflict Risk

STRIDE threat modeling is a fairly distinct niche with dedicated trigger terms, but 'analyzing system security' and 'creating security documentation' are broad enough to overlap with general security-review or audit skills. This matches 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/security-scanning/skills/stride-analysis-patterns/SKILL.md

Reviewed

Table of Contents

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.