Skills · Security

Attack Tree Construction

Unverified30/40

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

Originally by wshobson · MIT

Claude CodePartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
CursorPartialPlain prose you can paste in — but no Cursor rules file
CodexPartialPlain prose you can paste in — but no AGENTS.md
Gemini CLIPartialPlain prose you can paste in
CopilotPartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add attack-tree-construction

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

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

The whole source

No sign-in, no blur, nothing truncated
attack-tree-construction/SKILL.md75 lines2.6 KBRawView on GitHub
Frontmatter — 2 properties
nameattack-tree-construction
descriptionBuild comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
1---
2name: attack-tree-construction
3description: Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
4---A5No allowed-tools declared — no way to tell what this skill may touch
5 
6# Attack Tree Construction
7 
8Systematic attack path visualization and analysis.
9 
10## When to Use This Skill
11 
12- Visualizing complex attack scenarios
13- Identifying defense gaps and priorities
14- Communicating risks to stakeholders
15- Planning defensive investments
16- Penetration test planning
17- Security architecture review
18 
19## Core Concepts
20 
21### 1. Attack Tree Structure
22 
23```
24 [Root Goal]
25 |
26 ┌────────────┴────────────┐
27 │ │
28 [Sub-goal 1] [Sub-goal 2]
29 (OR node) (AND node)
30 │ │
31 ┌─────┴─────┐ ┌─────┴─────┐
32 │ │ │ │
33 [Attack] [Attack] [Attack] [Attack]
34 (leaf) (leaf) (leaf) (leaf)
35```
36 
37### 2. Node Types
38 
39| Type | Symbol | Description |
40| -------- | --------- | ----------------------- |
41| **OR** | Oval | Any child achieves goal |
42| **AND** | Rectangle | All children required |
43| **Leaf** | Box | Atomic attack step |
44 
45### 3. Attack Attributes
46 
47| Attribute | Description | Values |
48| ------------- | ----------------------- | ------------------ |
49| **Cost** | Resources needed | $, $$, $$$ |
50| **Time** | Duration to execute | Hours, Days, Weeks |
51| **Skill** | Expertise required | Low, Medium, High |
52| **Detection** | Likelihood of detection | Low, Medium, High |
53 
54## Templates and detailed worked examples
55 
56Full template library lives in `references/details.md`. Read that file when you need concrete templates for this skill.
57 
58## Best Practices
59 
60### Do's
61 
62- **Start with clear goals** - Define what attacker wants
63- **Be exhaustive** - Consider all attack vectors
64- **Attribute attacks** - Cost, skill, and detection
65- **Update regularly** - New threats emerge
66- **Validate with experts** - Red team review
67 
68### Don'ts
69 
70- **Don't oversimplify** - Real attacks are complex
71- **Don't ignore dependencies** - AND nodes matter
72- **Don't forget insider threats** - Not all attackers are external
73- **Don't skip mitigations** - Trees are for defense planning
74- **Don't make it static** - Threat landscape evolves
75 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Security