Individual skill

tradecraft-scope-roe

Establish and enforce the authorization envelope before any testing — the scope rule that governs everything. Load FIRST on every engagement, on "start", a new target, a program handle, or any ambiguity about what is allowed. Signals: a domain/IP to test, a bug-bounty program handle, a pentest statement of work, a scope list.

skills/tradecraft/tradecraft-scope-roe/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Oct 14, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
ai-security Repository topic
application-security Repository topic
blue-team Repository topic
bug-bounty Repository topic
claude-code Repository topic
codex Repository topic
detection-engineering Repository topic
gemini Repository topic
testing Derived category
security Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,135 bytes

Read excerpt


# Scope & Rules of Engagement (the hard rule)

## When this governs
Always, before the first packet. Security Skills operates only inside a confirmed authorization
envelope, and the envelope type is explicit. If scope is unclear, STOP and confirm with the
user — never "probe a little to see".

## The envelopes
- **Pentest / authorized engagement** — boundary is the signed scope: the statement of work /
  authorization letter naming the in-scope hosts, IP ranges, apps, and the testing window.
  Record the authorized targets in `scope.txt`; treat the window and any carve-outs as hard limits.
  (Practice ranges you own or are licensed to test — a home lab, a training range — count here.)
- **Bug-bounty program** — boundary is the **program scope + rules of engagement**. Before
  testing, capture: