Skip to content
Skills Library
Security · Planning

attack-tree-construction

/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.

Licence
MIT
Last repository change
07.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Original author description

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

How it works

  1. Use this skill when
  2. Do not use this skill when
  3. Instructions
  4. Safety
  5. Resources
Original SKILL.md headings · 35 lines, 153 words
SKILL.md preview
---
name: attack-tree-construction
description: Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
---

# 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.
Files in this package (2)
  • SKILL.md 1 KB
  • resources/implementation-playbook.md 21 KB

Versions

RepositoryScoreLicence
This page · rmyndharis/antigravity-skills100MIT
rootcastleco/rei-skills100MIT
wshobson/agents100MIT

Database snapshot: 13.11.2026 · package version 95bb88a49493 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100threat-modeling-techniques
    Threat modeling methodologies using STRIDE, attack trees, and risk assessment for proactive security analysis. Use when designing secure systems, conducting security reviews, or identifying potential attack vectors in applications.
  • 90threat-modeling
    Threat modeling skill for STRIDE analysis, attack tree construction, and security requirement extraction. Use when designing new features, reviewing architecture, conducting threat modeling sessions, creating security documentation, or training teams on security thinking.…
  • 100threat-modeling
    Run a structured threat-modeling session for a new feature, system, or architecture — STRIDE, attack trees, data flow diagrams, abuse cases. Use when the user mentions 'threat model,' 'threat modeling,' 'STRIDE,' 'attack tree,' 'abuse case,' 'data flow diagram,' 'DFD,' 'security…
  • 90threat-model
    Build a threat model from a synthesized CDK app: trust boundaries, entry points (APIs, distributions), which routes are callable without authorization, and candidate attack paths from an entry point to stored data, all as hypotheses. Use when the user asks for a threat model or…
  • 100security-audit
    Security-audit v2 workflow for application, repository, scoped path, PR, branch, or working-tree security review. Use for security audit, OWASP, secrets, threat model, attack path, Codex Security diff scan, release security gate, or security_change evidence requests.
  • 100attack-coverage-mapping
    Map detections and telemetry to MITRE ATT&CK, build ATT&CK Navigator layers, distinguish tested vs. claimed coverage, and prioritize gaps by threat relevance (threat-informed defense). Use when reporting detection coverage, planning a detection roadmap, or assessing readiness…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.