[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJSG25AH3W0Z131ZC78CNH":3,"skill-same:01M7EJSG25AH3W0Z131ZC78CNH":57},{"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":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7EJSG25AH3W0Z131ZC78CNH","conops-template",null,"Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.","a18268941610-crypto\u002FDecepticon-shentou","a18268941610-crypto","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F241464571?v=4","01M7EHA2V2KTCYTX78QJKXCZ8Y","fubai","01M7EHA2VKDD5RCWJJKC0ZA101",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Fconops-template\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conops-template\ndescription: \"Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.\"\nallowed-tools: Read Write Edit\nmetadata:\n  subdomain: planning\n  when_to_use: \"create CONOPS, design operation, threat model, plan attack\"\n  tags: conops, kill-chain, threat-model, operation-design\n  upstream_ref: \"Soundwave CONOPS template — Concept of Operations document generator\"\n---\n\n# Concept of Operations (CONOPS) Generator\n\nThe CONOPS bridges the legal RoE and the tactical OPPLAN. It must be **readable by a CEO** while containing **enough detail for operators**.\n\n## When to Use\n\n- After `plan\u002Froe.json` exists\n- User says \"create CONOPS\", \"design the operation\", \"build threat model\"\n- When the operator wants to design or revise a CONOPS. A direct Red run may build OPPLAN from the system RoE without this optional document.\n\n## Prerequisites\n\nRead `plan\u002Froe.json` first — scope and boundaries constrain the CONOPS.\n\nUse the active planning schema and the Soundwave system prompt for `CONOPS`, `ThreatActor`, `KillChainPhase`, and `DeconflictionPlan` fields. Skillogy returns this skill body without sibling reference files.\n\n## Workflow\n\n### Step 1: Interview the User\n\nUse the tier table and RoE Constraint→Profile Implication table in `threat-profile\u002FSKILL.md` to propose a threat profile. Ask the operator about material choices such as motivation, initial access, operation sequence, and success criteria when these are not already confirmed.\n\n**Question 1 — Threat actor tier** (single-select, use `threat-profile` skill for detailed profiling):\n   - a) Opportunistic external attacker (low)\n   - b) Targeted cybercriminal (medium)\n   - c) APT \u002F nation-state (high)\n   - d) Insider threat\n   - e) Custom — describe\n\nPropose **motivation** and **initial access vector** from the operator's confirmed context, then confirm them when they affect the operation.\n\n**Question 2 — Success criteria** — the crown-jewel \u002F measurable win condition. Required; no default (every engagement needs an explicit end-state).\n\n**Agent-drafted, not asked:**\n- **Attack narrative** — write the 2-3 sentence scenario yourself from RoE scope + tier + success criteria. This is the agent's job, not the operator's homework.\n- **Ultimate objectives** — derive from success criteria; do not ask as a separate dimension.\n- ~~Communication plan~~ — REMOVED. `CONOPS.communication_plan` is DEPRECATED (see SCHEMA_REFERENCE in soundwave.md); `ContactPlan` (contact-template skill) owns this now. Asking about it here duplicates a question and writes to a dead field.\n- **Deconfliction method** — default to standard red-team markers\u002Fheaders (see `deconfliction-template` reference) unless the operator's RoE\u002Fcontact answers already flagged a SOC integration endpoint; do not spend a dedicated question on it.\n\n### Step 2: Design Kill Chain\n\nBased on RoE scope + threat profile, select applicable phases using the active planning schema; do not depend on a sibling reference file that Skillogy cannot return.\n\n**Key rule**: Don't include phases outside RoE scope. Recon-only engagement → only `recon` phase.\n\n### Step 3: Generate Documents\n\n1. Create or revise `plan\u002Fconops.json` with the matching `CONOPS` schema.\n2. Create or revise `plan\u002Fdeconfliction.json` only when the operator is also designing that document; otherwise keep its existing content.\n\n### Step 4: Validate\n\n- Executive summary contains no jargon or tool names\n- Kill chain phases align with RoE scope\n- All MITRE ATT&CK technique IDs are valid\n- Timeline has concrete date ranges\n- At least 2 success criteria defined\n\n## Generation Rules\n\n1. **Executive summary = non-technical** — no tool names, no jargon\n2. **Threat actor TTPs must reference MITRE ATT&CK IDs**\n3. **Kill chain scoped to RoE** — no exploitation phase in recon-only engagement\n4. **Timeline uses absolute dates** — never relative\n5. **Deconfliction defaults to standard red-team markers\u002Fheaders** unless a SOC integration endpoint was already flagged; `communication_plan` is DEPRECATED — write coordination details to `ContactPlan` instead\n","# Concept of Operations (CONOPS) Generator\n\nThe CONOPS bridges the legal RoE and the tactical OPPLAN. It must be **readable by a CEO** while containing **enough detail for operators**.\n\n## When to Use\n\n- After `plan\u002Froe.json` exists\n- User says \"create CONOPS\", \"design the operation\", \"build threat model\"\n- When the operator wants to design or revise a CONOPS. A direct Red run may build OPPLAN from the system RoE without this optional document.\n\n## Prerequisites\n\nRead `plan\u002Froe.json` first — scope and boundaries constrain the CONOPS.\n\nUse the active planning schema and the Soundwave system prompt for `CONOPS`, `ThreatActor`, `KillChainPhase`, and `DeconflictionPlan` fields. Skillogy returns this skill body without sibling reference files.\n\n## Workflow\n\n### Step 1: Interview the User\n\nUse the tier table and RoE Constraint→Profile Implication table in `threat-profile\u002FSKILL.md` to propose a threat profile. Ask the operator about material choices such as motivation, initial access, operation sequence, and success criteria when these are not already confirmed.\n\n**Question 1 — Threat actor tier** (single-select, use `threat-profile` skill for detailed profiling):\n   - a) Opportunistic external attacker (low)\n   - b) Targeted cybercriminal (medium)\n   - c) APT \u002F nation-state (high)\n   - d) Insider threat\n   - e) Custom — describe\n\nPropose **motivation** and **initial access vector** from the operator's confirmed context, then confirm them when they affect the operation.\n\n**Question 2 — Success criteria** — the crown-jewel \u002F measurable win condition. Required; no default (every engagement needs an explicit end-state).\n\n**Agent-drafted, not asked:**\n- **Attack narrative** — write the 2-3 sentence scenario yourself from RoE scope + tier + success criteria. This is the agent's job, not the operator's homework.\n- **Ultimate objectives** — derive from success criteria; do not ask as a separate dimension.\n- ~~Communication plan~~ — REMOVED. `CONOPS.communication_plan` is DEPRECATED (see SCHEMA_REFERENCE in soundwave.md); `ContactPlan` (contact-template skill) owns this now. Asking about it here duplicates a question and writes to a dead field.\n- **Deconfliction method** — default to standard red-team markers\u002Fheaders (see `deconfliction-template` reference) unless the operator's RoE\u002Fcontact answers already flagged a SOC integration endpoint; do not spend a dedicated question on it.\n\n### Step 2: Design Kill Chain\n\nBased on RoE scope + threat profile, select applicable phases using the active planning schema; do not depend on a sibling reference file that Skillogy cannot return.\n\n**Key rule**: Don't include phases outside RoE scope. Recon-only engagement → only `recon` phase.\n\n### Step 3: Generate Documents\n\n1. Create or revise `plan\u002Fconops.json` with the matching `CONOPS` schema.\n2. Create or revise `plan\u002Fdeconfliction.json` only when the operator is also designing that document; otherwise keep its existing content.\n\n### Step 4: Validate\n\n- Executive summary contains no jargon or tool names\n- Kill chain phases align with RoE scope\n- All MITRE ATT&CK technique IDs are valid\n- Timeline has concrete date ranges\n- At least 2 success criteria defined\n\n## Generation Rules\n\n1. **Executive summary = non-technical** — no tool names, no jargon\n2. **Threat actor TTPs must reference MITRE ATT&CK IDs**\n3. **Kill chain scoped to RoE** — no exploitation phase in recon-only engagement\n4. **Timeline uses absolute dates** — never relative\n5. **Deconfliction defaults to standard red-team markers\u002Fheaders** unless a SOC integration endpoint was already flagged; `communication_plan` is DEPRECATED — write coordination details to `ContactPlan` instead\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"upstream_ref":28},"conops, kill-chain, threat-model, operation-design","planning","create CONOPS, design operation, threat model, plan attack","Soundwave CONOPS template — Concept of Operations document generator","Read Write Edit","main","d6bfd87ad9f910cfff715da04c804638990a8538","packages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Fconops-template",1,"https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto","2026-10-12 03:35:17",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add a18268941610-crypto\u002FDecepticon-shentou --skill conops-template",{"tool":43,"command":44},"bunx","bunx skills add a18268941610-crypto\u002FDecepticon-shentou --skill conops-template",{"tool":46,"command":47},"pnpm","pnpm dlx skills add a18268941610-crypto\u002FDecepticon-shentou --skill conops-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Fconops-template\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fkill-chain-templates.md","REFERENCE","参考文档",2855,"https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Fconops-template\u002Freferences\u002Fkill-chain-templates.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7EJXTEFYQPHY32431RWJENT","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\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EJXHKBXYF3QSYNW5YSK10H","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\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EJXAC5W1C1MACKKP1RRT8K","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\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EJX02A5FFBM2V7VG52GNSK","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\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EJWNRRMBRZQTKH3VFYAK58","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\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EJWB0CC58R8Z4HW6YRQCZW","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\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]