[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C2QFC9DMK5J74ENFFATZM":3,"skill-same:01M75C2QFC9DMK5J74ENFFATZM":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75C2QFC9DMK5J74ENFFATZM","cdo-review",null,"\u002Fcs:cdo-review \u003Cplan> — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcdo-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"cdo-review\"\ndescription: \"\u002Fcs:cdo-review \u003Cplan> — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring.\"\n---\n\n# \u002Fcs:cdo-review — CDO Forcing Questions\n\n**Command:** `\u002Fcs:cdo-review \u003Cplan>`\n\nThe decision-driven CDO pressure-tests any plan that touches data strategy. Six questions before any commitment to a data architecture, AI training run, data productization, or data team hire.\n\n## When to Run\n\n- Before approving any new ML model training run that uses customer data\n- Before signing a multi-year data-infrastructure SaaS contract (Snowflake, Databricks, Fivetran)\n- Before productizing any customer data (benchmark report, embedding endpoint, license)\n- Before a major data team hire (head of data, CDO, data PM, ML engineer)\n- Before M&A diligence — yours or theirs\n- When the founder uses the word \"monetize\" near \"data\"\n\n## The Six CDO Questions\n\n### 1. What decision does this data drive?\n**If no decision is unblocked, why are we collecting \u002F training on \u002F productizing it?**\n- \"We might need it later\" is not a decision.\n- \"It feels like a moat\" is not a decision.\n- A real answer names a specific business call that requires this data.\n\n### 2. What's the consent provenance for every source?\n**For each data source: origin, consent flow, data class, intended use.**\n- 1st-party-TOS-only is weaker than 1st-party-explicit-opt-in.\n- Bundled TOS doesn't cover material new purposes (training on PII for foundation models).\n- Run `ai_training_data_audit.py` if there's any AI use case in scope.\n\n### 3. Who consumes this internally — and how many distinct functional domains?\n**Drives the centralize-vs-embed and warehouse-vs-mesh decisions.**\n- \u003C5 consumers: warehouse-only.\n- 5-25 consumers: lakehouse.\n- 25+ consumers + federated culture: mesh.\n- Premature architecture choice is the #1 cause of data-team burnout.\n\n### 4. What's the M&A diligence impact?\n**If an acquirer asks about this data corpus tomorrow, are we ready?**\n- Is there a documented anonymization process?\n- What % of customers have MSA carve-outs?\n- Are training-data provenance logs current?\n- Run `data_asset_valuator.py` quarterly.\n\n### 5. Can the model \u002F decision \u002F report be retrained \u002F re-run \u002F re-published without this source?\n**Tests how much you depend on a specific data source.**\n- If yes → low blast radius; you can change consent posture later.\n- If no → high blast radius; you've structurally committed to the source. Vet harder.\n\n### 6. What role unblocks this — and is it the right next hire?\n**Wrong hire (data scientist) when right answer (analytics engineer) is a 12-month productivity loss.**\n- Map the decision being unblocked to the specific role.\n- Confirm prerequisite roles are in place (data engineer before ML engineer, analyst before data scientist).\n\n## Workflow\n\n```bash\n# 1. AI training audit (if any ML \u002F AI use case)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fai_training_data_audit.py sources.json\n\n# 2. Architecture decision (if changing the stack)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_product_strategy_picker.py profile.json\n\n# 3. Data asset valuation (if productizing or pre-M&A)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_asset_valuator.py corpus.json\n```\n\n## Output Format\n\n```markdown\n# CDO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — which of the four CDO decisions: training | architecture | asset | hire]\n\n## Training Audit (if applicable)\n- NO-GO sources: N\n- MITIGATE sources: N\n- GO sources: N\n- Top remediation: \u003Cone line>\n\n## Architecture (if applicable)\n- Recommended: WAREHOUSE \u002F LAKEHOUSE \u002F MESH\n- Build-vs-buy summary: \u003Cone line>\n- Kill criteria: \u003Cwhen to revisit>\n\n## Asset Value (if applicable)\n- Strategic value: X\u002F10 | Moat: STRONG \u002F MEDIUM \u002F WEAK\n- M&A multiplier: X.Xx – X.Xx ARR\n- Recommended productization path: \u003Cname>\n\n## Org (if applicable)\n- Next hire: \u003Crole>\n- Why this, not that: \u003Cone line>\n- Prerequisite hires in place: yes\u002Fno\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:gc-review` — for any productization or licensing path\n- `\u002Fcs:ciso-review` — for any architecture change touching customer data\n- `\u002Fcs:cfo-review` — for build-vs-buy TCO and M&A valuation math\n- `\u002Fcs:chro-review` — for data team hires (comp, ladder, leveling)\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 90` — on multi-year infrastructure contracts\n\n## Related\n\n- Agent: [`cs-cdo-advisor`](..\u002F..\u002Fagents\u002Fcs-cdo-advisor.md)\n- Skill: [`chief-data-officer-advisor`](..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002Fskills\u002Fgeneral-counsel-advisor\u002F` (contractual constraints), `..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002F` (architecture capacity)\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:cdo-review — CDO Forcing Questions\n\n**Command:** `\u002Fcs:cdo-review \u003Cplan>`\n\nThe decision-driven CDO pressure-tests any plan that touches data strategy. Six questions before any commitment to a data architecture, AI training run, data productization, or data team hire.\n\n## When to Run\n\n- Before approving any new ML model training run that uses customer data\n- Before signing a multi-year data-infrastructure SaaS contract (Snowflake, Databricks, Fivetran)\n- Before productizing any customer data (benchmark report, embedding endpoint, license)\n- Before a major data team hire (head of data, CDO, data PM, ML engineer)\n- Before M&A diligence — yours or theirs\n- When the founder uses the word \"monetize\" near \"data\"\n\n## The Six CDO Questions\n\n### 1. What decision does this data drive?\n**If no decision is unblocked, why are we collecting \u002F training on \u002F productizing it?**\n- \"We might need it later\" is not a decision.\n- \"It feels like a moat\" is not a decision.\n- A real answer names a specific business call that requires this data.\n\n### 2. What's the consent provenance for every source?\n**For each data source: origin, consent flow, data class, intended use.**\n- 1st-party-TOS-only is weaker than 1st-party-explicit-opt-in.\n- Bundled TOS doesn't cover material new purposes (training on PII for foundation models).\n- Run `ai_training_data_audit.py` if there's any AI use case in scope.\n\n### 3. Who consumes this internally — and how many distinct functional domains?\n**Drives the centralize-vs-embed and warehouse-vs-mesh decisions.**\n- \u003C5 consumers: warehouse-only.\n- 5-25 consumers: lakehouse.\n- 25+ consumers + federated culture: mesh.\n- Premature architecture choice is the #1 cause of data-team burnout.\n\n### 4. What's the M&A diligence impact?\n**If an acquirer asks about this data corpus tomorrow, are we ready?**\n- Is there a documented anonymization process?\n- What % of customers have MSA carve-outs?\n- Are training-data provenance logs current?\n- Run `data_asset_valuator.py` quarterly.\n\n### 5. Can the model \u002F decision \u002F report be retrained \u002F re-run \u002F re-published without this source?\n**Tests how much you depend on a specific data source.**\n- If yes → low blast radius; you can change consent posture later.\n- If no → high blast radius; you've structurally committed to the source. Vet harder.\n\n### 6. What role unblocks this — and is it the right next hire?\n**Wrong hire (data scientist) when right answer (analytics engineer) is a 12-month productivity loss.**\n- Map the decision being unblocked to the specific role.\n- Confirm prerequisite roles are in place (data engineer before ML engineer, analyst before data scientist).\n\n## Workflow\n\n```bash\n# 1. AI training audit (if any ML \u002F AI use case)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fai_training_data_audit.py sources.json\n\n# 2. Architecture decision (if changing the stack)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_product_strategy_picker.py profile.json\n\n# 3. Data asset valuation (if productizing or pre-M&A)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_asset_valuator.py corpus.json\n```\n\n## Output Format\n\n```markdown\n# CDO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — which of the four CDO decisions: training | architecture | asset | hire]\n\n## Training Audit (if applicable)\n- NO-GO sources: N\n- MITIGATE sources: N\n- GO sources: N\n- Top remediation: \u003Cone line>\n\n## Architecture (if applicable)\n- Recommended: WAREHOUSE \u002F LAKEHOUSE \u002F MESH\n- Build-vs-buy summary: \u003Cone line>\n- Kill criteria: \u003Cwhen to revisit>\n\n## Asset Value (if applicable)\n- Strategic value: X\u002F10 | Moat: STRONG \u002F MEDIUM \u002F WEAK\n- M&A multiplier: X.Xx – X.Xx ARR\n- Recommended productization path: \u003Cname>\n\n## Org (if applicable)\n- Next hire: \u003Crole>\n- Why this, not that: \u003Cone line>\n- Prerequisite hires in place: yes\u002Fno\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:gc-review` — for any productization or licensing path\n- `\u002Fcs:ciso-review` — for any architecture change touching customer data\n- `\u002Fcs:cfo-review` — for build-vs-buy TCO and M&A valuation math\n- `\u002Fcs:chro-review` — for data team hires (comp, ladder, leveling)\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 90` — on multi-year infrastructure contracts\n\n## Related\n\n- Agent: [`cs-cdo-advisor`](..\u002F..\u002Fagents\u002Fcs-cdo-advisor.md)\n- Skill: [`chief-data-officer-advisor`](..\u002F..\u002F..\u002Fskills\u002Fchief-data-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002Fskills\u002Fgeneral-counsel-advisor\u002F` (contractual constraints), `..\u002F..\u002F..\u002Fskills\u002Fcto-advisor\u002F` (architecture capacity)\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcdo-review",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill cdo-review",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill cdo-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill cdo-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcdo-review\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]