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

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/threat-mitigation-mapping/SKILL.md

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 body is concise and well-organized, but the instructions are generic and lack concrete, executable mapping guidance or a sequenced workflow. The referenced playbook file does not exist in the bundle, undermining the progressive disclosure structure.

Suggestions

Replace generic instructions with a concrete threat-to-control mapping method (e.g., map STRIDE or OWASP threat categories to specific control families like NIST CSF functions, with a short worked example).

Sequence the instructions as a numbered workflow with explicit validation checkpoints (e.g., map each threat to a control, verify the control addresses the threat's root cause, flag residual risk).

Create the referenced 'resources/implementation-playbook.md' file (or fix the path to match an existing references/ file) so the signaled progressive disclosure actually resolves.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanation of concepts Claude already knows; every section earns its place, matching 'lean and efficient; assumes Claude's competence'.	5 / 5
Actionability	The instructions are high-level hints — 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification' — with no concrete mapping method, framework, or example, matching 'minimal concrete guidance; high-level hints but missing the specific steps'.	2 / 5
Workflow Clarity	The four instruction bullets are parallel guidance rather than a sequenced workflow, with no numbered steps or validation checkpoints, matching 'rough sequence present but many gaps; validation absent'.	2 / 5
Progressive Disclosure	The body references one file — 'resources/implementation-playbook.md' — at a single level and signals it clearly, but no references/scripts/assets directories exist in the bundle, so the referenced resource is not actually present, leaving organization incomplete.	3 / 5
	Total	12 / 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.

The description is clear and well-structured, with an explicit 'Use when...' clause and concrete triggers that answer both what and when. It is slightly limited on specificity and trigger synonym coverage, but overall strong and low conflict risk.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — 'Map identified threats to appropriate security controls and mitigations' — but does not enumerate several specific actions, fitting the '1-2 concrete actions' anchor rather than the broader coverage of 4 or 5.	3 / 5
Completeness	It explicitly answers both 'what' (map threats to controls/mitigations) and 'when' (with concrete trigger phrases), matching the anchor for clearly and explicitly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	'Use when prioritizing security investments, creating remediation plans, or validating control effectiveness' provides three natural trigger phrases users would say, but it lacks common synonyms or variations, matching 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	'Threat mitigation mapping' is a fairly specific niche with distinct triggers, giving minimal conflict risk, but it still overlaps slightly with general security/risk skills, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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-mitigation-mapping/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.