How do I install the Tradecraft Scope Roe skill?

Run npx skillmds@latest add noorqureshi/tradecraft-scope-roe in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tradecraft Scope Roe safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tradecraft Scope Roe?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tradecraft Scope Roe free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tradecraft Scope Roe?

NoorQureshi (@noorqureshi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tradecraft Scope Roe by noorqureshi

Name: Tradecraft Scope Roe
Author: NoorQureshi

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.

NoorQureshi Updated Sep 17, 2026

File contents

Scope & Rules of Engagement (the hard rule)

When this governs

Always, before the first packet. SploitAgent 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:
- scope.txt — exact in-scope assets (domains, wildcards, IP ranges, apps) AND explicit out-of-scope. Out-of-scope is a hard block, not a suggestion.
- roe.md — allowed test types, rate limits, prohibited actions (no DoS, no social engineering unless allowed, no automated scanning if banned), data-handling rules, and the disclosure/safe-harbor terms.
Defensive work — you operate on systems your organization owns/authorizes; scope is the asset inventory you're permitted to assess/monitor.

The discipline

Confirm authorization and write the envelope files before scanning.
Match every target against in-scope patterns at request time; anything unmatched or out-of-scope is refused. Third parties (shared CDNs, SaaS the target merely uses) are out.
Respect RoE limits — throttle to the program's rate cap; skip prohibited techniques.
Minimize impact — prove the class with the least data/action; no lateral movement or data hoarding beyond what proves the finding; clean up artifacts (uploaded files, test accounts).
Mode-gate skills — honor each skill's modes:; a destructive technique safe only in a controlled pentest lab does not run against a live bugbounty production target.

Anti-patterns

"It resolved so it's probably in scope" — verify against the program's list.
Testing an acquisition/subsidiary not named in scope.
Ignoring rate limits because the bug is interesting.
Keeping real customer data as "evidence" instead of a redacted proof.

Verify

scope.txt (and roe.md for bug bounty) exist, the user confirmed authorization, and every planned action maps to an in-scope asset within the RoE.

References

Program policy pages; HackerOne/Bugcrowd RoE; disclose.io safe-harbor.

---name: tradecraft-scope-roedescription: 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.---# Scope & Rules of Engagement (the hard rule)## When this governsAlways, before the first packet. SploitAgent operates only inside a confirmed authorizationenvelope, and the envelope type is explicit. If scope is unclear, STOP and confirm with theuser — 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: - `scope.txt` — exact in-scope assets (domains, wildcards, IP ranges, apps) AND explicit out-of-scope. Out-of-scope is a hard block, not a suggestion. - `roe.md` — allowed test types, rate limits, prohibited actions (no DoS, no social engineering unless allowed, no automated scanning if banned), data-handling rules, and the disclosure/safe-harbor terms.- **Defensive work** — you operate on systems your organization owns/authorizes; scope is the asset inventory you're permitted to assess/monitor.## The discipline1. **Confirm authorization** and write the envelope files before scanning.2. **Match every target** against in-scope patterns at request time; anything unmatched or out-of-scope is refused. Third parties (shared CDNs, SaaS the target merely uses) are out.3. **Respect RoE limits** — throttle to the program's rate cap; skip prohibited techniques.4. **Minimize impact** — prove the class with the least data/action; no lateral movement or data hoarding beyond what proves the finding; clean up artifacts (uploaded files, test accounts).5. **Mode-gate skills** — honor each skill's `modes:`; a destructive technique safe only in a controlled `pentest` lab does not run against a live `bugbounty` production target.## Anti-patterns- "It resolved so it's probably in scope" — verify against the program's list.- Testing an acquisition/subsidiary not named in scope.- Ignoring rate limits because the bug is interesting.- Keeping real customer data as "evidence" instead of a redacted proof.## Verify`scope.txt` (and `roe.md` for bug bounty) exist, the user confirmed authorization, and everyplanned action maps to an in-scope asset within the RoE.## ReferencesProgram policy pages; HackerOne/Bugcrowd RoE; disclose.io safe-harbor.

Frequently asked questions