multiAI Summary Pending
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.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/attack-tree-construction/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/attack-tree-construction/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/attack-tree-construction/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How attack-tree-construction Compares
| Feature / Agent | attack-tree-construction | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Attack Tree Construction Systematic attack path visualization and analysis. ## Use this skill when - Visualizing complex attack scenarios - Identifying defense gaps and priorities - Communicating risks to stakeholders - Planning defensive investments or test scopes ## Do not use this skill when - You lack authorization or a defined scope to model the system - The task is a general risk review without attack-path modeling - The request is unrelated to security assessment or design ## Instructions - Confirm scope, assets, and the attacker goal for the root node. - Decompose into sub-goals with AND/OR structure. - Annotate leaves with cost, skill, time, and detectability. - Map mitigations per branch and prioritize high-impact paths. - If detailed templates are required, open `resources/implementation-playbook.md`. ## Safety - Share attack trees only with authorized stakeholders. - Avoid including sensitive exploit details unless required. ## Resources - `resources/implementation-playbook.md` for detailed patterns, templates, and examples.