Individual skill
roe-template
Read and interpret the system-provided Rules of Engagement while planning with the operator.
packages/decepticon/decepticon/skills/standard/soundwave/roe-template/SKILL.md
Source commit df879550544d36b6b1e69062f05adae28537adf2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 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)
- 6,575
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- cybersecurity Repository topic
- hacking Repository topic
- langchain Repository topic
- langgraph Repository topic
- llm Repository topic
- generative-ai Repository topic
- pentesting Repository topic
- pentest Repository topic
- roe,-scope,-engagement,-authorization Declared skill tag
- engineering 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 · 1,601 bytesreferences/roe-example.jsonasset · 1,968 bytesreferences/validation-checklist.mddoc · 1,243 bytes
Read excerpt
# Rules of Engagement in Plan mode
The product creates `plan/roe.json` from engagement setup and manages changes through its own UI and authorization controls. Soundwave may read it, but must never create, edit, replace, or sign it with filesystem tools. If it is absent, ask the operator to complete system setup outside Plan mode before planning target-facing work. If the operator wants a scope or exclusion change, direct them to the system-managed engagement settings; do not silently widen planning documents.
Read the existing RoE before writing other planning documents. Use its exact in-scope and out-of-scope targets, prohibited and permitted actions, authorization source, machine-enforcement rules, and any active time constraints. Do not invent an engagement type or a testing window when the system did not supply one. Ask the operator about choices for Soundwave-owned planning documents only when those choices remain material and unconfirmed.
The RoE constrains the threat profile, CONOPS, deconfliction, contact, data handling, abort, and cleanup documents. A planning draft or `complete_engagement_planning` call does not authorize a Red run or modify the RoE.