CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threat-mitigation-mapping

Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.

Quality

72%

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/threat-mitigation-mapping/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 with a verified, clearly signaled reference bundle, but the body spends its limited space re-teaching basic security concepts instead of giving a concrete mapping workflow. Adding an explicit step sequence for producing a threat-to-control mapping would substantially raise actionability and workflow clarity.

Suggestions

Add a short numbered workflow in the body (e.g., 1. enumerate threats, 2. map each to controls by layer/type using the control library, 3. score coverage and identify gaps, 4. produce the report from the templates in references/details.md) so execution doesn't depend on inferring the process from templates.

Cut or compress the 'Core Concepts' section (control categories, control layers, defense-in-depth diagrams) — this is standard security knowledge Claude already has; keep only the skill's own taxonomy conventions if they differ from standard usage.

Move the Do's/Don'ts bullets into the reference file or fold the few non-obvious ones (e.g., 'Track effectiveness', 'Don't ignore cost') into the workflow steps where they would be applied.

DimensionReasoningScore

Conciseness

The 'Core Concepts' section re-explains security fundamentals Claude already knows (preventive/detective/corrective control types, defense-in-depth layers with examples like 'Firewall, WAF') using two ASCII diagrams, which the guidelines penalize. However, the padding is confined to one compact section and the heavy detail is correctly offloaded to references, so it is mostly efficient rather than noticeably verbose.

3 / 5

Actionability

The body provides concrete taxonomies (the control-layer table, control-type examples) and a specific pointer to the template library in references/details.md, but contains no actual mapping procedure or worked steps of its own. Some concrete guidance exists, yet executing the task requires reconstructing the process from the reference file.

3 / 5

Workflow Clarity

No sequenced workflow appears in the body — the process (identify threats, map to controls, score coverage, report gaps) must be inferred from the templates in the reference file. A rough process is implied by the structure, but no explicit steps or checkpoints are stated, fitting the 'rough sequence with many gaps' anchor.

2 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled, one-level-deep reference: 'references/details.md' exists and contains exactly the enumerated templates (Mitigation Model, Defense in Depth scoring, Executive Summary, Critical Gaps, Recommendations, Implementation Roadmap, Results by Control). Content is appropriately split and navigation is easy.

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 strong description that clearly and explicitly states both what the skill does and when to use it, with concrete third-person trigger phrases. Its only gaps are a single-action 'what' clause and a few missing natural synonyms in the trigger terms.

DimensionReasoningScore

Specificity

'Map identified threats to appropriate security controls and mitigations' names the domain and one concrete action, but 'mitigations' restates the mapping rather than adding a second distinct action. It falls short of anchor 4, which requires several specific listed actions.

3 / 5

Completeness

The description explicitly answers both questions: a clear third-person 'what' ('Map identified threats to appropriate security controls and mitigations') and an explicit 'Use when' clause with three concrete trigger scenarios, matching the anchor 5 example pattern. Anchor 4's caveat that the 'when' could be more explicit does not apply.

5 / 5

Trigger Term Quality

'prioritizing security investments', 'creating remediation plans', and 'validating control effectiveness' are natural phrases users would say. Coverage is good but misses common synonyms such as 'risk treatment', 'control mapping', or 'threat model', so it does not reach the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The threat-to-control mapping niche is mostly distinct with specific triggers, but 'prioritizing security investments' is broad enough to also fire a generic risk-assessment or security-audit skill, creating minor overlap risk with closely related skills rather than the minimal conflict of anchor 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/threat-mitigation-mapping/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.