[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DGF780EAFBBCJZD83TFXN1":3,"skill-same:01M7DGF780EAFBBCJZD83TFXN1":56},{"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},"01M7DGF780EAFBBCJZD83TFXN1","conops-template",null,"Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.","Akapi895\u002Fraptix","Akapi895","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83953516?v=4","01M7DEGNDGERR4F4YETDFVA512","Phạm Anh Tuấn","01M7DEGNEHYZNA920AYM5EH7H8",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\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- Before OPPLAN can be generated\n\n## Prerequisites\n\nRead `plan\u002Froe.json` first — scope and boundaries constrain the CONOPS.\n\nSee `..\u002Freferences\u002Fschema-quick-reference.md` for the `CONOPS`, `ThreatActor`, `KillChainPhase`, and `DeconflictionPlan` schema fields.\n\n## Workflow\n\n### Step 1: Interview the User\n\n**Budget: 2 questions max for CONOPS\u002FThreat Profile** (soundwave.md CRITICAL_RULES → Question Budget). The remaining fields below are DEFAULTED or AGENT-DRAFTED, not asked — the tier table and RoE Constraint→Profile Implication table in `threat-profile\u002FSKILL.md` already give deterministic defaults for motivation and initial access once the tier is picked, so re-asking them wastes a turn.\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\nDerive **motivation** and **initial access vector** from the picked tier via `threat-profile\u002Freferences\u002Fadversary-archetypes.md` (default) — do not ask separately. Only deviate if the operator's free-text answer (via `allow_other`) already states a motivation\u002Fvector explicitly.\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. See `references\u002Fkill-chain-templates.md`.\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. `plan\u002Fconops.json` — matching `CONOPS` schema\n2. `plan\u002Fdeconfliction.json` — matching `DeconflictionPlan` schema\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- Before OPPLAN can be generated\n\n## Prerequisites\n\nRead `plan\u002Froe.json` first — scope and boundaries constrain the CONOPS.\n\nSee `..\u002Freferences\u002Fschema-quick-reference.md` for the `CONOPS`, `ThreatActor`, `KillChainPhase`, and `DeconflictionPlan` schema fields.\n\n## Workflow\n\n### Step 1: Interview the User\n\n**Budget: 2 questions max for CONOPS\u002FThreat Profile** (soundwave.md CRITICAL_RULES → Question Budget). The remaining fields below are DEFAULTED or AGENT-DRAFTED, not asked — the tier table and RoE Constraint→Profile Implication table in `threat-profile\u002FSKILL.md` already give deterministic defaults for motivation and initial access once the tier is picked, so re-asking them wastes a turn.\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\nDerive **motivation** and **initial access vector** from the picked tier via `threat-profile\u002Freferences\u002Fadversary-archetypes.md` (default) — do not ask separately. Only deviate if the operator's free-text answer (via `allow_other`) already states a motivation\u002Fvector explicitly.\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. See `references\u002Fkill-chain-templates.md`.\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. `plan\u002Fconops.json` — matching `CONOPS` schema\n2. `plan\u002Fdeconfliction.json` — matching `DeconflictionPlan` schema\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","master","8e5d356b795eae2edd4a26509a4b8968e2c4c251","packages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fsoundwave\u002Fconops-template","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix","https:\u002F\u002Fgithub.com\u002FAkapi895","2026-11-06 17:46:09",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Akapi895\u002Fraptix --skill conops-template",{"tool":42,"command":43},"bunx","bunx skills add Akapi895\u002Fraptix --skill conops-template",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Akapi895\u002Fraptix --skill conops-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fsoundwave\u002Fconops-template\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fkill-chain-templates.md","REFERENCE","参考文档",2855,"https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fsoundwave\u002Fconops-template\u002Freferences\u002Fkill-chain-templates.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7DGM32SRP4FZSPYWY621BKQ","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\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DGKXXVDTY0KBZZR83VFPZX","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\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7DGKSV77ENX3D6TG2HQX9MK","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\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DGKJ9R6YTFRFBSEAJRGGKF","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\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DGKCFZGKK2EQMWZM1A18S8","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\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DGK76MKZQWBXTZN82W7214","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\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]