attack-tree-construction

Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.

Quality

80%

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/attack-tree-construction/SKILL.md

Quality

Content

77%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 concise, well-structured, and provides clear actionable steps with a strong validation gate. The primary weakness is progressive disclosure: it references a playbook file that is absent, leaving the 'detailed templates' pointer broken.

Suggestions

Add the missing `resources/implementation-playbook.md` (or correct the path to the actual bundle file) so the reference resolves.

Consolidate the duplicated 'AUTHORIZED USE ONLY' notices into a single warning block to tighten the body.

Consider whether the playbook should live under the conventional `references/` directory and update both the Instructions and Resources sections consistently.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no over-explanation of concepts Claude already knows, though the 'AUTHORIZED USE ONLY' warning is restated twice and could be trimmed.	4 / 5
Actionability	Concrete, specific instructions (confirm scope, decompose into AND/OR sub-goals, annotate leaves with cost/skill/time/detectability) with only minor gaps; the confirmation gate is highly actionable.	4 / 5
Workflow Clarity	Clear sequence from scoping through decomposition to mitigation mapping, plus an explicit validation checkpoint (the numbered mandatory confirmation gate) and a 'stop and ask' feedback loop.	5 / 5
Progressive Disclosure	Section structure is good, but the sole reference to `resources/implementation-playbook.md` points to a file that does not exist (no resources/ directory present), a meaningful navigation defect.	3 / 5
	Total	16 / 20 Passed

Description

82%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 strong, clearly answering both what the skill does and when to use it with natural trigger phrases and a distinct niche. Main weakness is specificity, which lists only two actions rather than comprehensive coverage.

Suggestions

Add a couple more concrete verbs to the 'what' clause (e.g., 'analyze, prioritize, and document attack paths') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("Build comprehensive attack trees", "visualize threat paths") but does not enumerate the full action set, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Explicitly states what it does (build attack trees to visualize threat paths) and when to use it (concrete 'Use when...' trigger clauses), matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases users would say appear ("mapping attack scenarios", "identifying defense gaps", "communicating security risks") with good coverage, though some synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (attack tree construction) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/attack-tree-construction/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours 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.