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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 sensibly sectioned with a clear when/when-not structure, but it stays abstract without concrete examples or validation checkpoints, and its only progressive-disclosure reference points to a non-existent file.

Suggestions

Add a small inline example attack-tree fragment (root node with one AND and one OR branch and annotated leaves) so the guidance is concrete and copyable.

Create the referenced `resources/implementation-playbook.md` (or remove the dangling references) so progressive-disclosure links resolve to real files.

Insert an explicit validation/verification checkpoint (e.g. "confirm every leaf is annotated and every mitigation maps to a high-impact path before sharing").

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept re-explanation; sections like Instructions and Safety are terse and every line carries guidance, matching the lean-and-efficient anchor.	3 / 3
Actionability	Guidance is specific ("Decompose into sub-goals with AND/OR structure", "Annotate leaves with cost, skill, time, and detectability") but stays abstract with no concrete example, template fragment, or worked node to copy, leaving it short of fully executable guidance.	2 / 3
Workflow Clarity	Five sequenced steps are listed, but there are no explicit validation checkpoints or feedback loops, and the conditional "If detailed templates are required, open..." branch lacks clear pass/fail criteria.	2 / 3
Progressive Disclosure	The body signals a one-level reference to `resources/implementation-playbook.md` in Instructions and Resources, but no `resources/` directory or bundle file exists, so the referenced path is broken rather than a well-organized external resource.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 concise, well-formed description that clearly states capability and provides an explicit use-trigger with a distinct niche. The only weakness is trigger-term coverage, which leans on domain jargon and misses common phrasings like "threat modeling".

Suggestions

Broaden trigger terms to include natural user phrasings such as "threat modeling", "threat paths", or "risk scenarios" to improve discoverability.

Consider adding a tangible output cue (e.g. "produce an AND/OR attack-tree diagram") to make the concrete action even more specific.

Dimension	Reasoning	Score
Specificity	"Build comprehensive attack trees to visualize threat paths" plus "mapping attack scenarios, identifying defense gaps, or communicating security risks" lists multiple concrete actions within a defined domain, matching the multiple-specific-actions anchor.	3 / 3
Completeness	It states what the skill does ("Build comprehensive attack trees...") and an explicit "Use when..." trigger clause answering when to invoke it, satisfying both halves.	3 / 3
Trigger Term Quality	Terms like "attack trees", "attack scenarios", "defense gaps", and "security risks" are relevant but lean toward domain jargon and omit common natural variations a user might say (e.g. "threat model", "threat modeling"), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The attack-tree-construction niche has distinct triggers (attack trees, threat paths, defense gaps) unlikely to collide with other skills, fitting the clear-niche anchor.	3 / 3
	Total	11 / 12 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: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 days 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.