菜单
Rules of Engagement document creation — scope definition, prohibited/permitted actions, testing windows, escalation contacts, incident procedures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Red team engagement lifecycle management — initiation, phase transitions, go/no-go gates, deconfliction, emergency procedures, completion.
Mandatory first-turn startup procedure — checks for existing engagements, resume/new selection, workspace initialization.
Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.
Decepticon orchestrator patterns — delegation, state management, adaptive re-planning, context handoff protocols.
Use when setting up, running, or managing the Botron autonomous red team agent — Docker-based multi-provider LLM pentesting framework. Covers install, demo, service management, testing, and provider configuration.
Sliver C2 framework operations — server connection, listener setup, implant generation, BOF/Armory extensions, post-implant operations, HTTP C2 profiles.
| name | roe-template |
| description | Rules of Engagement document creation — scope definition, prohibited/permitted actions, testing windows, escalation contacts, incident procedures. |
| allowed-tools | Read Write Edit |
| metadata | {"subdomain":"planning","when_to_use":"create RoE, define scope, engagement boundaries, start new engagement","tags":"roe, scope, engagement, authorization, legal","mitre_attack":[]} |
The RoE is the legally binding foundation of every red team engagement. All other documents build on it.
Ask these questions in two rounds (batch related questions to minimize back-and-forth):
Round 1 — Identity & Scope:
external / internal / hybrid / assumed-breach / physicalRound 2 — Boundaries & Escalation: 6. Additional prohibited actions beyond defaults 7. Special permitted actions (phishing, password spraying, etc.) 8. Escalation contacts (minimum 2: client + red team lead) — name, role, channel 9. Authorization reference (contract #, signed letter)
Use the RoE schema from botron.core.schemas. Write to the engagement directory.
See references/roe-example.json for a complete example and ../references/schema-quick-reference.md for all required fields and valid values.
Run through the checklist in references/validation-checklist.md before presenting to user.
Write roe.json to the engagement directory, then present a human-readable summary to the user for confirmation.