[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M770S0V62H3M7W1NH09SNJSZ":3,"skill-same:01M770S0V62H3M7W1NH09SNJSZ":50},{"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},"01M770S0V62H3M7W1NH09SNJSZ","data-handling-template",null,"Data handling plan generator — evidence retention, encryption, chain-of-custody, compliance frameworks (GDPR \u002F HIPAA \u002F PCI-DSS \u002F SOC2).","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\u002Fdata-handling-template\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: data-handling-template\ndescription: \"Data handling plan generator — evidence retention, encryption, chain-of-custody, compliance frameworks (GDPR \u002F HIPAA \u002F PCI-DSS \u002F SOC2).\"\nallowed-tools: Read Write Edit\nmetadata:\n  subdomain: planning\n  when_to_use: \"create data handling plan, evidence retention, chain-of-custody, GDPR, HIPAA, PCI-DSS, compliance, PII handling\"\n  tags: data-handling, evidence, retention, encryption, chain-of-custody, compliance, gdpr, hipaa\n  upstream_ref: \"Soundwave data-handling template — evidence retention, encryption, chain-of-custody, compliance\"\n---\n\n# Data Handling Plan Generator\n\nThe data handling plan defines **what evidence the agent collects, where it lives, how long it's kept, and who can read it**. Replaces the deprecated free-form `RoE.data_handling` string with structured per-class fields.\n\n## When to Use\n\n- After RoE is written (RoE constraints + scope drive which data classes appear)\n- User says \"create data handling\", \"retention policy\", \"evidence storage\", \"PII handling\", \"compliance\"\n\n## Workflow\n\n### Step 1: Start From the Schema Defaults\n\nThe `DataHandlingPlan` schema seeds four default classes — credentials, pii, source-code, business-data — with conservative retention. **Keep these by default**; override only when the engagement requires stricter or looser rules.\n\n### Step 2: Add Engagement-Specific Classes\n\nBased on the interview:\n\n| Engagement type | Likely additional classes |\n|---|---|\n| Healthcare client | `health-records` (classification: secret, retention: 7 days, framework: HIPAA) |\n| Financial client | `cardholder-data` (classification: secret, retention: 0 days — never store, framework: PCI-DSS) |\n| EU client \u002F data subjects | Mark existing `pii` with framework: GDPR; consider `personal-data-eu` for stricter handling |\n| Defense \u002F classified | `controlled-unclassified` (classification: secret, retention: 0 days off-network) |\n\n### Step 3: Set Evidence Storage Path\n\nDefault `\"\u002Fworkspace\u002F\u003Cengagement>\u002Fevidence\u002F\"` works for sandbox-isolated engagements. Override only when:\n- Engagement requires an external-bucket destination (S3 \u002F Azure Blob with client KMS)\n- Multiple engagement workspaces share an evidence repository\n\n### Step 4: Compliance Frameworks\n\nSet `compliance_frameworks` from the interview. Common entries: GDPR, HIPAA, PCI-DSS, SOC2, NIST 800-53, FedRAMP, ISO 27001.\n\nThe orchestrator (Decepticon) reads this list and refuses to start objectives that violate the matching framework's evidence-handling rules.\n\n### Step 5: Purge Hard Cap\n\n`purge_after_days` is the GLOBAL upper bound — every artifact older than this is deleted regardless of per-class retention. Default 90 days; reduce for engagements with tighter regulatory exposure.\n\n## Validation Checklist\n\nBefore writing `plan\u002Fdata-handling.json`:\n\n- [ ] At least one `data_class` is `credentials`-equivalent\n- [ ] Every class has `retention_days >= 0`\n- [ ] `purge_after_days >= max(class.retention_days)` (otherwise classes get cut short)\n- [ ] If `compliance_frameworks` includes HIPAA \u002F GDPR \u002F PCI-DSS, matching data classes exist\n- [ ] `chain_of_custody=True` for any engagement that may produce findings\n\n## Anti-patterns\n\n- Setting `retention_days=0` for `credentials` without explicit operator approval — agent then can't reference creds across phases\n- Disabling `encryption_at_rest` for any restricted+ class — straight compliance violation\n- Listing HIPAA in `compliance_frameworks` without a `health-records` class — orchestrator will refuse objectives that touch PHI\n\n## Output\n\nWrite to `plan\u002Fdata-handling.json` validating against `decepticon.core.schemas.DataHandlingPlan`.\n","# Data Handling Plan Generator\n\nThe data handling plan defines **what evidence the agent collects, where it lives, how long it's kept, and who can read it**. Replaces the deprecated free-form `RoE.data_handling` string with structured per-class fields.\n\n## When to Use\n\n- After RoE is written (RoE constraints + scope drive which data classes appear)\n- User says \"create data handling\", \"retention policy\", \"evidence storage\", \"PII handling\", \"compliance\"\n\n## Workflow\n\n### Step 1: Start From the Schema Defaults\n\nThe `DataHandlingPlan` schema seeds four default classes — credentials, pii, source-code, business-data — with conservative retention. **Keep these by default**; override only when the engagement requires stricter or looser rules.\n\n### Step 2: Add Engagement-Specific Classes\n\nBased on the interview:\n\n| Engagement type | Likely additional classes |\n|---|---|\n| Healthcare client | `health-records` (classification: secret, retention: 7 days, framework: HIPAA) |\n| Financial client | `cardholder-data` (classification: secret, retention: 0 days — never store, framework: PCI-DSS) |\n| EU client \u002F data subjects | Mark existing `pii` with framework: GDPR; consider `personal-data-eu` for stricter handling |\n| Defense \u002F classified | `controlled-unclassified` (classification: secret, retention: 0 days off-network) |\n\n### Step 3: Set Evidence Storage Path\n\nDefault `\"\u002Fworkspace\u002F\u003Cengagement>\u002Fevidence\u002F\"` works for sandbox-isolated engagements. Override only when:\n- Engagement requires an external-bucket destination (S3 \u002F Azure Blob with client KMS)\n- Multiple engagement workspaces share an evidence repository\n\n### Step 4: Compliance Frameworks\n\nSet `compliance_frameworks` from the interview. Common entries: GDPR, HIPAA, PCI-DSS, SOC2, NIST 800-53, FedRAMP, ISO 27001.\n\nThe orchestrator (Decepticon) reads this list and refuses to start objectives that violate the matching framework's evidence-handling rules.\n\n### Step 5: Purge Hard Cap\n\n`purge_after_days` is the GLOBAL upper bound — every artifact older than this is deleted regardless of per-class retention. Default 90 days; reduce for engagements with tighter regulatory exposure.\n\n## Validation Checklist\n\nBefore writing `plan\u002Fdata-handling.json`:\n\n- [ ] At least one `data_class` is `credentials`-equivalent\n- [ ] Every class has `retention_days >= 0`\n- [ ] `purge_after_days >= max(class.retention_days)` (otherwise classes get cut short)\n- [ ] If `compliance_frameworks` includes HIPAA \u002F GDPR \u002F PCI-DSS, matching data classes exist\n- [ ] `chain_of_custody=True` for any engagement that may produce findings\n\n## Anti-patterns\n\n- Setting `retention_days=0` for `credentials` without explicit operator approval — agent then can't reference creds across phases\n- Disabling `encryption_at_rest` for any restricted+ class — straight compliance violation\n- Listing HIPAA in `compliance_frameworks` without a `health-records` class — orchestrator will refuse objectives that touch PHI\n\n## Output\n\nWrite to `plan\u002Fdata-handling.json` validating against `decepticon.core.schemas.DataHandlingPlan`.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"upstream_ref":28},"data-handling, evidence, retention, encryption, chain-of-custody, compliance, gdpr, hipaa","planning","create data handling plan, evidence retention, chain-of-custody, GDPR, HIPAA, PCI-DSS, compliance, PII handling","Soundwave data-handling template — evidence retention, encryption, chain-of-custody, compliance","Read Write Edit","main","c0c483827a963764d5e1a663a9591867d47289e6","stack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Fdata-handling-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 data-handling-template",{"tool":42,"command":43},"bunx","bunx skills add Iwakishirokoshu\u002FHermesUltimate --skill data-handling-template",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Iwakishirokoshu\u002FHermesUltimate --skill data-handling-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fsoundwave\u002Fdata-handling-template\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":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},"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":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},"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":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},"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":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},"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":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},"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",[],[]]