CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threat-modeling-expert

Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture reviews, threat identification, and secure-by-design planning.

Quality

76%

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 ./skills/threat-modeling-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body is well-organized and token-efficient with a clear 8-step threat modeling process, but it operates at a purely abstract level: no methodology specifics, scoring techniques, examples, or templates that would make the guidance executable, and the workflow lacks validation checkpoints. It is an instruction-only skill, so the absence of code is not penalized — the issue is that the instructions add little beyond naming a process Claude already knows.

Suggestions

Make the Instructions concrete: add a STRIDE-per-element mapping (e.g., a compact table of which STRIDE categories apply to processes/data stores/data flows) and specify a threat scoring method such as likelihood × impact or DREAD so 'Score and prioritize threats' is executable.

Include a brief example artifact — a filled-in mini attack tree or a few lines of a completed threat model entry (threat, STRIDE category, risk score, mitigation, residual risk) — so Claude knows exactly what output to produce.

Add validation checkpoints to the workflow, e.g., 'Before prioritizing, confirm all six STRIDE categories were applied to every element in scope' and 'Review the prioritized threat list with developers before designing mitigations'.

DimensionReasoningScore

Conciseness

The body is mostly lean lists with no explanation of concepts Claude already knows (STRIDE is never defined — good). Not 5 because of trimmable redundancy: the intro paragraph repeats the frontmatter description verbatim, "Keep threat models updated after architecture changes" (Safety) duplicates "Update threat models with architecture changes" (Best Practices), and "Review regularly, not just at design time" overlaps both; not 3 because there is no padding or unnecessary explanation.

4 / 5

Actionability

Quotes: "Apply STRIDE to each component", "Score and prioritize threats", "Create data flow diagrams" — the steps name activities but give no specifics on how to execute them (no STRIDE-per-element mapping, no scoring method like likelihood×impact or DREAD, no example threat model or output template). Matches anchor 2 (high-level hints missing the specific steps); not 3 because there is no partially-concrete artifact such as pseudocode, an example, or a template anywhere; not 1 because the eight imperative steps do instruct rather than merely describe.

2 / 5

Workflow Clarity

Quotes: "1. Define system scope and trust boundaries ... 8. Document residual risks" — a clear, sensible 8-step sequence. Not 4/5 because no validation checkpoints exist (nothing like "confirm all six STRIDE categories were covered per element before prioritizing" or "review the threat list with developers before designing mitigations"), matching anchor 3 (sequence present but checkpoints missing); not 2 because the sequence is complete and coherent, not rough or gappy.

3 / 5

Progressive Disclosure

The body is a short, single-purpose skill (~40 content lines) with clean, well-signaled sections (Capabilities / Use when / Instructions / Safety / Best Practices), no external references needed, and nothing inlined that belongs in a separate file — matching the simple-skill exception. Not 4 because there are no organization gaps: every section is scannable and appropriately placed.

5 / 5

Total

14

/

20

Passed

Description

83%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 strong description that clearly states both what the skill does and when to use it, with concrete trigger scenarios and distinctive methodology names (STRIDE, PASTA, attack trees). It is written in third person and avoids fluff, with only minor gaps in natural-keyword synonyms and slight overlap risk with general security-review skills.

DimensionReasoningScore

Specificity

Quotes: "security architecture review, and risk assessment", "Masters STRIDE, PASTA, attack trees, and security requirement extraction", "threat identification, and secure-by-design planning" — several concrete capabilities named across the domain. Not 5 because "Masters STRIDE, PASTA" names methodologies rather than actions and reads slightly as a capability claim; not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Quotes: what — "Expert in threat modeling methodologies, security architecture review, and risk assessment"; when — "Use for security architecture reviews, threat identification, and secure-by-design planning". Both are explicitly and clearly answered with concrete trigger phrases, matching the anchor-5 pattern; the "Use for" clause is explicit so the completeness cap of 3 does not apply.

5 / 5

Trigger Term Quality

Quotes: "Use for security architecture reviews, threat identification, and secure-by-design planning" plus named methodologies ("STRIDE, PASTA, attack trees") — good keyword coverage with phrases users would naturally say. Not 5 because common variations like "threat model this system", "security audit", or "risk analysis" are missing; not 3 because the natural terms present go beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

Quotes: "threat modeling methodologies", "STRIDE, PASTA, attack trees", "secure-by-design planning" — a clear niche with distinctive methodology names. Not 5 because broader phrases like "security architecture review" and "risk assessment" carry minor overlap risk with a general security-review skill; not 3 because STRIDE/PASTA/attack-tree triggers anchor it firmly in threat modeling.

4 / 5

Total

17

/

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

rmyndharis/antigravity-skills

Path

skills/threat-modeling-expert/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.