CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-threat-model

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

2.54x
Quality

91%

Does it follow best practices?

Impact

94%

2.54x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is a tight, actionable eight-step workflow with explicit user-validation and quality checkpoints, and it makes good use of two one-level-deep reference files. The main weaknesses are minor: a duplicated asset enumeration between steps 2 and 3, and delegation of concrete output examples to the referenced prompt template. It aligns closely with the rubric's good examples.

Suggestions

Merge the asset lists in steps 2 and 3 into a single step to remove the duplicated enumeration (data, credentials, models, config, compute resources vs. credentials, PII, integrity-critical state, etc.).

Include one compact inline example of a prioritized threat entry (goal, likelihood, impact, priority) so the expected output shape is visible without opening the reference file.

Fix the sentence fragment in the opening paragraph ("Prioritizing realistic attacker goals and concrete impacts over generic checklists") by attaching it to the previous sentence.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains what threat modeling or trust boundaries are — but step 3 ("List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts)") substantially duplicates the asset listing already in step 2, and the opening paragraph has a dangling fragment ("Prioritizing realistic attacker goals..."). These are minor trim candidates consistent with the level-4 anchor rather than the fully lean level-5 anchor.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: named control types ("authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging"), a specific good-vs-generic contrast ("enforce schema at gateway for upload payloads" vs "validate inputs"), and an explicit output filename pattern ("<repo-or-dir-name>-threat-model.md"). It sits at level 4 rather than 5 because worked examples of a prioritized threat entry and the full output format are delegated to the reference file, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

Eight clearly sequenced steps include explicit validation checkpoints: step 6 is a user feedback loop ("Pause and wait for user feedback before producing the final report", with a defined fallback if the user can't answer) and step 8 is a literal pre-finalize quality checklist. This matches the level-5 anchor (clear sequence, explicit validation, feedback loops, checklists) rather than level 4's 'most checkpoints, minor gaps'.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview (Quick start, Workflow, Risk guidance, References) that appropriately pushes the full output contract and controls checklist into two real, verified one-level-deep reference files, each clearly labeled with its purpose, and closes with "Only load the reference files you need." This matches the level-5 anchor: well-signaled shallow references with content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

92%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.

The description is specific, uses third person, and explicitly answers both what the skill does and when to invoke it, with concrete positive and negative trigger guidance. Keyword coverage is strong though not exhaustive of domain synonyms. It compares favorably to the good examples in the rubric.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model" — comprehensively covering the skill's function including the output artifact. It exceeds the level-4 anchor ('several specific actions; minor gaps') because the enumeration categories plus the deliverable cover the whole task.

5 / 5

Completeness

Both questions are answered explicitly: the first sentence gives a clear 'what', and "Trigger only when the user explicitly asks to threat model a codebase or path..." gives a concrete 'when' with specific trigger phrases, matching the level-5 anchor. It is not level 4 because the 'when' clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "threat model a codebase or path", "enumerate threats/abuse paths", "AppSec threat modeling" — which users would genuinely say. It falls short of the level-5 anchor because common synonyms such as "attack surface" or "STRIDE" are absent, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear AppSec threat-modeling niche and adds negative triggers — "Do not trigger for general architecture summaries, code review, or non-security design work" — minimizing conflict with adjacent skills. This fits the level-5 anchor (clear niche, distinct triggers, minimal conflict) rather than level 4's 'minor overlap risk'.

5 / 5

Total

19

/

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

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/security-threat-model/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.