[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M770S9QCVAR9NZAS6Y0STG4F":3,"skill-same:01M770S9QCVAR9NZAS6Y0STG4F":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M770S9QCVAR9NZAS6Y0STG4F","roe-template",null,"Rules of Engagement document creation — scope definition, prohibited\u002Fpermitted actions, testing windows, escalation contacts, incident procedures.","Iwakishirokoshu\u002FHermesUltimate","Iwakishirokoshu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194847626?v=4","01M75P4CVGA89TTCE8JGMNAQQ9","Around","01M75P4CWF85V6GVSEFKGGFZ03",0,"MIT","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Froe-template\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: roe-template\ndescription: \"Rules of Engagement document creation — scope definition, prohibited\u002Fpermitted actions, testing windows, escalation contacts, incident procedures.\"\nallowed-tools: Read Write Edit\nmetadata:\n  subdomain: planning\n  when_to_use: \"create RoE, define scope, engagement boundaries, start new engagement\"\n  tags: roe, scope, engagement, authorization, legal\n  upstream_ref: \"Soundwave Rules of Engagement template — scope \u002F window \u002F escalation \u002F incident procedures\"\n---\n\n# Rules of Engagement (RoE) Generator\n\nThe RoE is the **legally binding** foundation of every red team engagement. All other documents build on it.\n\n## When to Use\n\n- Starting a new engagement\n- User says \"create RoE\", \"define scope\", \"set boundaries\"\n- Before any other planning document can be created\n\n## Workflow\n\n### Step 1: Interview the User\n\nDrive each dimension through one `ask_user_question` call (per CRITICAL_RULES #8 — every operator-facing question goes through the tool). Cover these roughly in order, never bundling multiple questions in one turn:\n\n**Identity & Scope**\n1. Engagement name (free-form, `allow_other=true` with sensible guesses)\n2. Client organization (free-form, `allow_other=true`)\n3. Engagement type — single-select: `external` \u002F `internal` \u002F `hybrid` \u002F `assumed-breach` \u002F `physical`\n4. Start date \u002F end date \u002F testing window with timezone (free-form, `allow_other=true` — suggest defaults like \"Mon-Fri 09:00-18:00 client TZ\")\n5. In-scope targets (free-form, `allow_other=true` — domains, IP ranges, cloud resources, applications)\n6. Out-of-scope targets (free-form, `allow_other=true`)\n\n**Boundaries & Escalation**\n7. Additional prohibited actions beyond schema defaults (multi-select with sensible options + `allow_other=true`)\n8. Special permitted actions — phishing, password spraying, raw-socket scans (multi-select)\n9. Escalation contacts — minimum 2 (client + red team lead). One ask per contact slot covering name, role, channel\n10. Authorization reference \u002F contract # (free-form, `allow_other=true`)\n\n### Step 2: Generate plan\u002Froe.json\n\nUse the `RoE` schema from `decepticon.core.schemas`. Write to the engagement directory.\n\nSee `references\u002Froe-example.json` for a complete example and `..\u002Freferences\u002Fschema-quick-reference.md` for all required fields and valid values.\n\n### Step 3: Validate\n\nRun through the checklist in `references\u002Fvalidation-checklist.md` before presenting to user.\n\n## Generation Rules\n\n1. **Always include default prohibited actions** — DoS, unauthorized social engineering, unauthorized physical access, real data exfiltration, production data modification\n2. **Scope must be specific** — CIDR notation for IPs, wildcard notation for domains\n3. **Testing window must include timezone**\n4. **At least 2 escalation contacts** required\n5. **Authorization reference must not be empty**\n\n## Output\n\nWrite `plan\u002Froe.json` to the engagement directory, then present a human-readable summary to the user for confirmation.\n","# Rules of Engagement (RoE) Generator\n\nThe RoE is the **legally binding** foundation of every red team engagement. All other documents build on it.\n\n## When to Use\n\n- Starting a new engagement\n- User says \"create RoE\", \"define scope\", \"set boundaries\"\n- Before any other planning document can be created\n\n## Workflow\n\n### Step 1: Interview the User\n\nDrive each dimension through one `ask_user_question` call (per CRITICAL_RULES #8 — every operator-facing question goes through the tool). Cover these roughly in order, never bundling multiple questions in one turn:\n\n**Identity & Scope**\n1. Engagement name (free-form, `allow_other=true` with sensible guesses)\n2. Client organization (free-form, `allow_other=true`)\n3. Engagement type — single-select: `external` \u002F `internal` \u002F `hybrid` \u002F `assumed-breach` \u002F `physical`\n4. Start date \u002F end date \u002F testing window with timezone (free-form, `allow_other=true` — suggest defaults like \"Mon-Fri 09:00-18:00 client TZ\")\n5. In-scope targets (free-form, `allow_other=true` — domains, IP ranges, cloud resources, applications)\n6. Out-of-scope targets (free-form, `allow_other=true`)\n\n**Boundaries & Escalation**\n7. Additional prohibited actions beyond schema defaults (multi-select with sensible options + `allow_other=true`)\n8. Special permitted actions — phishing, password spraying, raw-socket scans (multi-select)\n9. Escalation contacts — minimum 2 (client + red team lead). One ask per contact slot covering name, role, channel\n10. Authorization reference \u002F contract # (free-form, `allow_other=true`)\n\n### Step 2: Generate plan\u002Froe.json\n\nUse the `RoE` schema from `decepticon.core.schemas`. Write to the engagement directory.\n\nSee `references\u002Froe-example.json` for a complete example and `..\u002Freferences\u002Fschema-quick-reference.md` for all required fields and valid values.\n\n### Step 3: Validate\n\nRun through the checklist in `references\u002Fvalidation-checklist.md` before presenting to user.\n\n## Generation Rules\n\n1. **Always include default prohibited actions** — DoS, unauthorized social engineering, unauthorized physical access, real data exfiltration, production data modification\n2. **Scope must be specific** — CIDR notation for IPs, wildcard notation for domains\n3. **Testing window must include timezone**\n4. **At least 2 escalation contacts** required\n5. **Authorization reference must not be empty**\n\n## Output\n\nWrite `plan\u002Froe.json` to the engagement directory, then present a human-readable summary to the user for confirmation.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"upstream_ref":28},"roe, scope, engagement, authorization, legal","planning","create RoE, define scope, engagement boundaries, start new engagement","Soundwave Rules of Engagement template — scope \u002F window \u002F escalation \u002F incident procedures","Read Write Edit","main","c0c483827a963764d5e1a663a9591867d47289e6","stack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Froe-template","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu","2026-06-15 13:48:41",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Iwakishirokoshu\u002FHermesUltimate --skill roe-template",{"tool":42,"command":43},"bunx","bunx skills add Iwakishirokoshu\u002FHermesUltimate --skill roe-template",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Iwakishirokoshu\u002FHermesUltimate --skill roe-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Froe-template\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Froe-example.json","REFERENCE","参考文档",1968,"https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Froe-template\u002Freferences\u002Froe-example.json",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fvalidation-checklist.md",1243,"https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Froe-template\u002Freferences\u002Fvalidation-checklist.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M770W8JDE5EC1TJT4GSDWD78","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M770W4B7T5VCVHB88V1F02H1","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M770W093C8FAV8S34K8VB6T9","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M770VTNAQGZ3D0RQVFEKTE8Z","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M770VNG05ZX3CV84R9GX8PJN","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M770VHFH7N192V56PFSRXF5K","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]