[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754JZ5DCW4GEKSWAFAAZJT1":3,"skill-same:01M754JZ5DCW4GEKSWAFAAZJT1":83},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M754JZ5DCW4GEKSWAFAAZJT1","chief-data-officer-advisor",null,"Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data architecture, valuing data for fundraising or M&A, sequencing data hires, or when user mentions CDO, chief data officer, data strategy, data mesh, lakehouse, training data, data product, data monetization, or customer data asset. NOT a tactical data engineering skill — strategic decisions only.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"chief-data-officer-advisor\"\ndescription: \"Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data architecture, valuing data for fundraising or M&A, sequencing data hires, or when user mentions CDO, chief data officer, data strategy, data mesh, lakehouse, training data, data product, data monetization, or customer data asset. NOT a tactical data engineering skill — strategic decisions only.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: chief-data-officer-leadership\n  updated: 2026-05-12\n  python-tools: ai_training_data_audit.py, data_product_strategy_picker.py, data_asset_valuator.py\n  frameworks: training-data-rights-matrix, data-product-strategy, customer-data-as-asset, data-team-org-evolution\n---\n\n# Chief Data Officer Advisor\n\nStrategic data leadership for startup CDOs and founders without one. **Four decisions, no surveys:**\n\n1. **Can we train our model on this data?** — origin × consent × use-case matrix\n2. **Warehouse, lakehouse, or mesh — and what do we build vs buy?** — stage-driven architecture\n3. **What is our customer data worth?** — strategic value + M&A multiplier + productization paths\n4. **What data role do we hire next?** — stage-to-role map, centralize-vs-embed trigger\n\nThis skill does **not** cover tactical data engineering. For schema design, observability, query optimization, RAG, or ML platform implementation, see `engineering\u002Fdatabase-designer\u002F`, `engineering\u002Fobservability-designer\u002F`, `engineering\u002Fdata-quality-auditor\u002F`, `engineering\u002Fsql-database-assistant\u002F`, `engineering\u002Frag-architect\u002F`, `engineering\u002Fllm-cost-optimizer\u002F`.\n\n## Keywords\n\nCDO, chief data officer, AI training data, consent provenance, training rights, GDPR Article 6 lawful basis, GDPR Article 22, EU AI Act high-risk, ePrivacy, copyright fair use, hiQ v. LinkedIn, scraped data, synthetic data, data product, data mesh, lakehouse, medallion architecture, dbt, Snowflake, BigQuery, Databricks, Fivetran, Airbyte, reverse ETL, feature store, customer data as asset, data monetization, data productization, anonymization, k-anonymity, differential privacy, M&A data diligence, data org, analytics engineer, data engineer, data scientist, data product manager, centralize vs embed, hub and spoke\n\n## Quick Start\n\n```bash\n# Audit data sources for AI training eligibility\npython scripts\u002Fai_training_data_audit.py                              # uses embedded sample\npython scripts\u002Fai_training_data_audit.py path\u002Fto\u002Fsources.json\n\n# Pick data architecture + build-vs-buy + sequencing\npython scripts\u002Fdata_product_strategy_picker.py                        # uses embedded Series A SaaS\npython scripts\u002Fdata_product_strategy_picker.py path\u002Fto\u002Fprofile.json\n\n# Value the customer data corpus + productization viability\npython scripts\u002Fdata_asset_valuator.py                                 # uses embedded B2B sample\npython scripts\u002Fdata_asset_valuator.py path\u002Fto\u002Fcorpus.json\n```\n\n## Key Questions (ask these first)\n\n- **What decision does this data drive?** (If none, why are we collecting it?)\n- **What's the consent provenance of every source we want to train on?** (TOS-only is not the same as explicit opt-in.)\n- **Who are the internal data consumers, and how many distinct domains do they span?** (Drives centralize-vs-embed and warehouse-vs-mesh.)\n- **In an M&A scenario, is our data a moat or a liability?** (Customer carve-outs in MSAs can flip the answer.)\n- **Are we hiring an analytics engineer or a data scientist next?** (They solve different problems; founders confuse them.)\n- **Have we run an anonymization audit before any external sharing?** (k-anonymity ≥ 5 is the floor, not the ceiling.)\n\n## Core Responsibilities\n\n### 1. AI Training Data Rights\n\nThe 2026 question every startup is facing: **can we use customer data to train our model?**\n\nThe answer is rarely binary. It depends on three independent dimensions:\n\n| Dimension | Values |\n|---|---|\n| **Origin** | 1st-party-explicit-opt-in \u002F 1st-party-TOS-only \u002F partner-licensed \u002F scraped \u002F synthetic |\n| **Data class** | Anonymous aggregate \u002F behavioral \u002F PII \u002F 3rd-party content \u002F regulated (PHI, PCI, kids) |\n| **Use case** | In-product personalization \u002F fine-tune our model \u002F train foundation model \u002F external sharing |\n\nEach combination produces GO \u002F MITIGATE \u002F NO-GO. **Run** `ai_training_data_audit.py` on a JSON inventory of sources.\n\nSee `references\u002Fai_training_data_rights.md` for the full matrix + GDPR Art. 6 lawful basis decision tree + EU AI Act high-risk triggers.\n\n### 2. Data Product Strategy\n\n**Architecture choice (warehouse vs lakehouse vs mesh) is stage-driven, not preference-driven:**\n\n- **Warehouse only** (Snowflake \u002F BigQuery \u002F Postgres): ≤5 data consumers, \u003C2TB, no ML use cases\n- **Lakehouse** (warehouse + object storage, often Databricks or Snowflake-with-Iceberg): 5–25 data consumers, 2TB–1PB, 1–3 ML use cases\n- **Data mesh**: 25+ data consumers across 4+ domains, federated ownership culture in place\n\n**Build vs buy is decided per layer:**\n\n| Layer | Buy unless | Build only if |\n|---|---|---|\n| Storage \u002F warehouse | Never build | (You’re a data infra company) |\n| ELT \u002F ingest | Never build | Source isn’t supported by Fivetran\u002FAirbyte |\n| Modeling (dbt) | Always build | This is your IP |\n| BI \u002F dashboards | Buy at \u003C100 consumers | Embedded analytics for customers |\n| Feature store | Defer until 3+ prod models | Then build OR buy Tecton\u002FHopsworks |\n| ML platform | Defer until 5+ prod models | Then buy SageMaker\u002FVertex\u002FDatabricks |\n\n**Run** `data_product_strategy_picker.py` for a stage-specific recommendation. See `references\u002Fdata_product_strategy.md` for kill criteria per architecture and the build-vs-buy decision tree.\n\n### 3. B2B Customer-Data-as-Asset\n\n**The shift:** at Series B+, customer data is no longer just operational — it’s an asset that can be:\n- A defensibility moat (replicating requires years of customer cohort)\n- An M&A multiplier (1.2x–2x ARR uplift for strategic buyers)\n- A direct revenue stream (anonymized industry benchmarks, embedding endpoints, licensing)\n\nBut it can also be a **liability**:\n- 47\u002F380 customers with MSA carve-outs makes productization legally infeasible\n- Anonymization audits often reveal re-identification risk above tolerable thresholds\n- Regulatory exposure increases linearly with productization (GDPR Art. 28 processors vs Art. 26 joint controllers)\n\n**Run** `data_asset_valuator.py` with corpus characteristics to get strategic value score + productization paths + risk-adjusted value.\n\nSee `references\u002Fcustomer_data_as_asset.md` for the valuation framework, M&A diligence prep checklist, and contractual constraint audit pattern.\n\n### 4. Data Team Org Evolution\n\n**The wrong question:** \"Should we hire a data scientist?\"\n**The right question:** \"What’s the next decision we can’t make because we lack data, and what role unblocks that?\"\n\nStage-to-role map (B2B SaaS baseline):\n\n| Stage | First hire | Then | Then |\n|---|---|---|---|\n| Pre-seed \u002F seed | Founder-as-analyst (SQL + spreadsheets) | — | — |\n| Series A (Series A) | Analyst | Analytics engineer (dbt) | — |\n| Series B | Data engineer | Senior analyst (embedded in GTM) | Data PM (if 3+ teams need data) |\n| Growth | Manager of analytics | ML engineer (if model is core) | Head of Data |\n| Late-stage | Head of Data → CDO | Specialized: BI, MLE, DPO | Federated owners per domain (mesh) |\n\n**Centralize-vs-embed trigger:** when 3+ functional areas (sales, marketing, product, ops, CS) need bespoke data weekly, the central team becomes the bottleneck. Move to hub-and-spoke (central platform + embedded analysts) before that becomes a hiring crisis.\n\nSee `references\u002Fdata_team_org_evolution.md`.\n\n## Workflows\n\n### Workflow 1: AI Training Decision (1 hour)\n**Goal:** Decide whether a specific data source can train a specific use case.\n\n```bash\n# 1. Build sources.json with one entry per data source\n# 2. Run the audit\npython scripts\u002Fai_training_data_audit.py sources.json\n# 3. For each MITIGATE: assign owner + remediation\n# 4. For each NO-GO: document the kill reason for the legal log\n# 5. Cross-check with cs-general-counsel-advisor on top-3 mitigation items\n# 6. Log via \u002Fcs:decide\n```\n\n### Workflow 2: Architecture Decision (1 day)\n**Goal:** Pick warehouse \u002F lakehouse \u002F mesh and the build-vs-buy split for the next 12 months.\n\n```bash\npython scripts\u002Fdata_product_strategy_picker.py profile.json\n# Cross-check with cs-cto-advisor on engineering capacity\n# Cross-check with cs-cfo-advisor on 3-year TCO\n# Log via \u002Fcs:decide; consider \u002Fcs:freeze 90 if signing a multi-year SaaS contract\n```\n\n### Workflow 3: Data Asset Valuation for M&A Prep (3 days)\n**Goal:** Value the data corpus and prepare for due diligence.\n\n1. Inventory the corpus: size, freshness, exclusivity, customer overlap, contractual restrictions\n2. Run `data_asset_valuator.py`\n3. Run the M&A diligence prep checklist in `customer_data_as_asset.md`\n4. Surface contractual carve-outs to cs-general-counsel-advisor for re-papering plan\n5. Decide productization path (benchmark report \u002F embedding endpoint \u002F direct license)\n6. Log via \u002Fcs:decide\n\n### Workflow 4: Data Team Roadmap (1 week)\n**Goal:** Build the next 18 months of data hires aligned to business decisions.\n\n1. List the top 5 decisions the business can’t make today due to missing data or analysis\n2. Map each decision to the role that unblocks it\n3. Sequence hires (one role at a time, ramp before next)\n4. Cross-check with cs-chro-advisor on comp bands and leveling\n5. Identify the centralize-vs-embed trigger date\n\n## Output Standards (when invoked via cs-cdo-advisor)\n\n```\n**Bottom Line:** [one sentence — decision and rationale]\n**The Decision:** [one of the 4 framings]\n**The Evidence:** [numbers, not adjectives]\n**How to Act:** [3 concrete next steps]\n**Your Decision:** [the call only the founder can make]\n```\n\n## Adjacent Skills\n\n- `..\u002Fcto-advisor\u002F` — architecture capacity, scaling cliffs\n- `..\u002Fciso-advisor\u002F` — data security, threat modeling for productized data\n- `..\u002Fgeneral-counsel-advisor\u002F` — contractual constraints, DPA, training-data rights\n- `..\u002Fcfo-advisor\u002F` — build-vs-buy TCO, M&A valuation math\n- `..\u002Fchro-advisor\u002F` — data team hiring, leveling, comp\n- `..\u002F..\u002F..\u002Fengineering\u002Fdatabase-designer\u002F` — tactical schema design\n- `..\u002F..\u002F..\u002Fengineering\u002Frag-architect\u002F` — tactical AI\u002FRAG implementation\n- `..\u002F..\u002F..\u002Fengineering\u002Fllm-cost-optimizer\u002F` — model cost management\n\n## References\n\n- [ai_training_data_rights.md](references\u002Fai_training_data_rights.md) — The training-rights matrix + GDPR Art. 6 \u002F EU AI Act decision tree\n- [data_product_strategy.md](references\u002Fdata_product_strategy.md) — Warehouse \u002F lakehouse \u002F mesh kill criteria + build-vs-buy decision tree\n- [customer_data_as_asset.md](references\u002Fcustomer_data_as_asset.md) — Valuation framework + M&A diligence prep + productization paths\n- [data_team_org_evolution.md](references\u002Fdata_team_org_evolution.md) — Stage-to-role map + centralize-vs-embed trigger\n\n---\n\n**Version:** 1.0.0\n**Status:** Production Ready\n**Disclaimer:** Decisions touching training data rights, data productization, or M&A data diligence should involve qualified counsel. This skill surfaces decisions and tradeoffs — it does not replace legal review.\n","# Chief Data Officer Advisor\n\nStrategic data leadership for startup CDOs and founders without one. **Four decisions, no surveys:**\n\n1. **Can we train our model on this data?** — origin × consent × use-case matrix\n2. **Warehouse, lakehouse, or mesh — and what do we build vs buy?** — stage-driven architecture\n3. **What is our customer data worth?** — strategic value + M&A multiplier + productization paths\n4. **What data role do we hire next?** — stage-to-role map, centralize-vs-embed trigger\n\nThis skill does **not** cover tactical data engineering. For schema design, observability, query optimization, RAG, or ML platform implementation, see `engineering\u002Fdatabase-designer\u002F`, `engineering\u002Fobservability-designer\u002F`, `engineering\u002Fdata-quality-auditor\u002F`, `engineering\u002Fsql-database-assistant\u002F`, `engineering\u002Frag-architect\u002F`, `engineering\u002Fllm-cost-optimizer\u002F`.\n\n## Keywords\n\nCDO, chief data officer, AI training data, consent provenance, training rights, GDPR Article 6 lawful basis, GDPR Article 22, EU AI Act high-risk, ePrivacy, copyright fair use, hiQ v. LinkedIn, scraped data, synthetic data, data product, data mesh, lakehouse, medallion architecture, dbt, Snowflake, BigQuery, Databricks, Fivetran, Airbyte, reverse ETL, feature store, customer data as asset, data monetization, data productization, anonymization, k-anonymity, differential privacy, M&A data diligence, data org, analytics engineer, data engineer, data scientist, data product manager, centralize vs embed, hub and spoke\n\n## Quick Start\n\n```bash\n# Audit data sources for AI training eligibility\npython scripts\u002Fai_training_data_audit.py                              # uses embedded sample\npython scripts\u002Fai_training_data_audit.py path\u002Fto\u002Fsources.json\n\n# Pick data architecture + build-vs-buy + sequencing\npython scripts\u002Fdata_product_strategy_picker.py                        # uses embedded Series A SaaS\npython scripts\u002Fdata_product_strategy_picker.py path\u002Fto\u002Fprofile.json\n\n# Value the customer data corpus + productization viability\npython scripts\u002Fdata_asset_valuator.py                                 # uses embedded B2B sample\npython scripts\u002Fdata_asset_valuator.py path\u002Fto\u002Fcorpus.json\n```\n\n## Key Questions (ask these first)\n\n- **What decision does this data drive?** (If none, why are we collecting it?)\n- **What's the consent provenance of every source we want to train on?** (TOS-only is not the same as explicit opt-in.)\n- **Who are the internal data consumers, and how many distinct domains do they span?** (Drives centralize-vs-embed and warehouse-vs-mesh.)\n- **In an M&A scenario, is our data a moat or a liability?** (Customer carve-outs in MSAs can flip the answer.)\n- **Are we hiring an analytics engineer or a data scientist next?** (They solve different problems; founders confuse them.)\n- **Have we run an anonymization audit before any external sharing?** (k-anonymity ≥ 5 is the floor, not the ceiling.)\n\n## Core Responsibilities\n\n### 1. AI Training Data Rights\n\nThe 2026 question every startup is facing: **can we use customer data to train our model?**\n\nThe answer is rarely binary. It depends on three independent dimensions:\n\n| Dimension | Values |\n|---|---|\n| **Origin** | 1st-party-explicit-opt-in \u002F 1st-party-TOS-only \u002F partner-licensed \u002F scraped \u002F synthetic |\n| **Data class** | Anonymous aggregate \u002F behavioral \u002F PII \u002F 3rd-party content \u002F regulated (PHI, PCI, kids) |\n| **Use case** | In-product personalization \u002F fine-tune our model \u002F train foundation model \u002F external sharing |\n\nEach combination produces GO \u002F MITIGATE \u002F NO-GO. **Run** `ai_training_data_audit.py` on a JSON inventory of sources.\n\nSee `references\u002Fai_training_data_rights.md` for the full matrix + GDPR Art. 6 lawful basis decision tree + EU AI Act high-risk triggers.\n\n### 2. Data Product Strategy\n\n**Architecture choice (warehouse vs lakehouse vs mesh) is stage-driven, not preference-driven:**\n\n- **Warehouse only** (Snowflake \u002F BigQuery \u002F Postgres): ≤5 data consumers, \u003C2TB, no ML use cases\n- **Lakehouse** (warehouse + object storage, often Databricks or Snowflake-with-Iceberg): 5–25 data consumers, 2TB–1PB, 1–3 ML use cases\n- **Data mesh**: 25+ data consumers across 4+ domains, federated ownership culture in place\n\n**Build vs buy is decided per layer:**\n\n| Layer | Buy unless | Build only if |\n|---|---|---|\n| Storage \u002F warehouse | Never build | (You’re a data infra company) |\n| ELT \u002F ingest | Never build | Source isn’t supported by Fivetran\u002FAirbyte |\n| Modeling (dbt) | Always build | This is your IP |\n| BI \u002F dashboards | Buy at \u003C100 consumers | Embedded analytics for customers |\n| Feature store | Defer until 3+ prod models | Then build OR buy Tecton\u002FHopsworks |\n| ML platform | Defer until 5+ prod models | Then buy SageMaker\u002FVertex\u002FDatabricks |\n\n**Run** `data_product_strategy_picker.py` for a stage-specific recommendation. See `references\u002Fdata_product_strategy.md` for kill criteria per architecture and the build-vs-buy decision tree.\n\n### 3. B2B Customer-Data-as-Asset\n\n**The shift:** at Series B+, customer data is no longer just operational — it’s an asset that can be:\n- A defensibility moat (replicating requires years of customer cohort)\n- An M&A multiplier (1.2x–2x ARR uplift for strategic buyers)\n- A direct revenue stream (anonymized industry benchmarks, embedding endpoints, licensing)\n\nBut it can also be a **liability**:\n- 47\u002F380 customers with MSA carve-outs makes productization legally infeasible\n- Anonymization audits often reveal re-identification risk above tolerable thresholds\n- Regulatory exposure increases linearly with productization (GDPR Art. 28 processors vs Art. 26 joint controllers)\n\n**Run** `data_asset_valuator.py` with corpus characteristics to get strategic value score + productization paths + risk-adjusted value.\n\nSee `references\u002Fcustomer_data_as_asset.md` for the valuation framework, M&A diligence prep checklist, and contractual constraint audit pattern.\n\n### 4. Data Team Org Evolution\n\n**The wrong question:** \"Should we hire a data scientist?\"\n**The right question:** \"What’s the next decision we can’t make because we lack data, and what role unblocks that?\"\n\nStage-to-role map (B2B SaaS baseline):\n\n| Stage | First hire | Then | Then |\n|---|---|---|---|\n| Pre-seed \u002F seed | Founder-as-analyst (SQL + spreadsheets) | — | — |\n| Series A (Series A) | Analyst | Analytics engineer (dbt) | — |\n| Series B | Data engineer | Senior analyst (embedded in GTM) | Data PM (if 3+ teams need data) |\n| Growth | Manager of analytics | ML engineer (if model is core) | Head of Data |\n| Late-stage | Head of Data → CDO | Specialized: BI, MLE, DPO | Federated owners per domain (mesh) |\n\n**Centralize-vs-embed trigger:** when 3+ functional areas (sales, marketing, product, ops, CS) need bespoke data weekly, the central team becomes the bottleneck. Move to hub-and-spoke (central platform + embedded analysts) before that becomes a hiring crisis.\n\nSee `references\u002Fdata_team_org_evolution.md`.\n\n## Workflows\n\n### Workflow 1: AI Training Decision (1 hour)\n**Goal:** Decide whether a specific data source can train a specific use case.\n\n```bash\n# 1. Build sources.json with one entry per data source\n# 2. Run the audit\npython scripts\u002Fai_training_data_audit.py sources.json\n# 3. For each MITIGATE: assign owner + remediation\n# 4. For each NO-GO: document the kill reason for the legal log\n# 5. Cross-check with cs-general-counsel-advisor on top-3 mitigation items\n# 6. Log via \u002Fcs:decide\n```\n\n### Workflow 2: Architecture Decision (1 day)\n**Goal:** Pick warehouse \u002F lakehouse \u002F mesh and the build-vs-buy split for the next 12 months.\n\n```bash\npython scripts\u002Fdata_product_strategy_picker.py profile.json\n# Cross-check with cs-cto-advisor on engineering capacity\n# Cross-check with cs-cfo-advisor on 3-year TCO\n# Log via \u002Fcs:decide; consider \u002Fcs:freeze 90 if signing a multi-year SaaS contract\n```\n\n### Workflow 3: Data Asset Valuation for M&A Prep (3 days)\n**Goal:** Value the data corpus and prepare for due diligence.\n\n1. Inventory the corpus: size, freshness, exclusivity, customer overlap, contractual restrictions\n2. Run `data_asset_valuator.py`\n3. Run the M&A diligence prep checklist in `customer_data_as_asset.md`\n4. Surface contractual carve-outs to cs-general-counsel-advisor for re-papering plan\n5. Decide productization path (benchmark report \u002F embedding endpoint \u002F direct license)\n6. Log via \u002Fcs:decide\n\n### Workflow 4: Data Team Roadmap (1 week)\n**Goal:** Build the next 18 months of data hires aligned to business decisions.\n\n1. List the top 5 decisions the business can’t make today due to missing data or analysis\n2. Map each decision to the role that unblocks it\n3. Sequence hires (one role at a time, ramp before next)\n4. Cross-check with cs-chro-advisor on comp bands and leveling\n5. Identify the centralize-vs-embed trigger date\n\n## Output Standards (when invoked via cs-cdo-advisor)\n\n```\n**Bottom Line:** [one sentence — decision and rationale]\n**The Decision:** [one of the 4 framings]\n**The Evidence:** [numbers, not adjectives]\n**How to Act:** [3 concrete next steps]\n**Your Decision:** [the call only the founder can make]\n```\n\n## Adjacent Skills\n\n- `..\u002Fcto-advisor\u002F` — architecture capacity, scaling cliffs\n- `..\u002Fciso-advisor\u002F` — data security, threat modeling for productized data\n- `..\u002Fgeneral-counsel-advisor\u002F` — contractual constraints, DPA, training-data rights\n- `..\u002Fcfo-advisor\u002F` — build-vs-buy TCO, M&A valuation math\n- `..\u002Fchro-advisor\u002F` — data team hiring, leveling, comp\n- `..\u002F..\u002F..\u002Fengineering\u002Fdatabase-designer\u002F` — tactical schema design\n- `..\u002F..\u002F..\u002Fengineering\u002Frag-architect\u002F` — tactical AI\u002FRAG implementation\n- `..\u002F..\u002F..\u002Fengineering\u002Fllm-cost-optimizer\u002F` — model cost management\n\n## References\n\n- [ai_training_data_rights.md](references\u002Fai_training_data_rights.md) — The training-rights matrix + GDPR Art. 6 \u002F EU AI Act decision tree\n- [data_product_strategy.md](references\u002Fdata_product_strategy.md) — Warehouse \u002F lakehouse \u002F mesh kill criteria + build-vs-buy decision tree\n- [customer_data_as_asset.md](references\u002Fcustomer_data_as_asset.md) — Valuation framework + M&A diligence prep + productization paths\n- [data_team_org_evolution.md](references\u002Fdata_team_org_evolution.md) — Stage-to-role map + centralize-vs-embed trigger\n\n---\n\n**Version:** 1.0.0\n**Status:** Production Ready\n**Disclaimer:** Decisions touching training data rights, data productization, or M&A data diligence should involve qualified counsel. This skill surfaces decisions and tradeoffs — it does not replace legal review.\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","chief-data-officer-leadership",1778544000000,"1.0.0","c-level","training-data-rights-matrix, data-product-strategy, customer-data-as-asset, data-team-org-evolution","ai_training_data_audit.py, data_product_strategy_picker.py, data_asset_valuator.py","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add ASoudy\u002FAGS --skill chief-data-officer-advisor",{"tool":43,"command":44},"bunx","bunx skills add ASoudy\u002FAGS --skill chief-data-officer-advisor",{"tool":46,"command":47},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill chief-data-officer-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002FSKILL.md",true,[51,57,61,65,69,75,79],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fai_training_data_rights.md","REFERENCE","参考文档",7365,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Freferences\u002Fai_training_data_rights.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcustomer_data_as_asset.md",10285,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Freferences\u002Fcustomer_data_as_asset.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdata_product_strategy.md",8612,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Freferences\u002Fdata_product_strategy.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fdata_team_org_evolution.md",10446,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Freferences\u002Fdata_team_org_evolution.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fai_training_data_audit.py","SCRIPT","脚本",19434,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fai_training_data_audit.py",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fdata_asset_valuator.py",14664,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_asset_valuator.py",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fdata_product_strategy_picker.py",14828,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fchief-data-officer-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_product_strategy_picker.py",[84,91,98,105,112,119],{"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},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]