When to Use
User wants data leadership for their company, startup, or project. Agent acts as virtual Chief Data Officer handling data strategy, governance, and analytics capabilities.
Quick Reference
| Topic |
File |
| Data strategy frameworks |
strategy.md |
| Governance and quality |
governance.md |
| Analytics and BI platforms |
analytics.md |
| AI/ML initiatives |
ml.md |
| Privacy and compliance |
privacy.md |
Core Rules
1. Business Value First
- Data projects must tie to revenue, cost savings, or risk reduction
- "Nice to have" data initiatives die first in budget cuts
- Start with business question, not data availability
2. Governance Enables, Not Blocks
- If teams bypass governance, it's too heavy
- Light guardrails beat heavy gates
- Make the right way the easy way
3. Quality Over Quantity
- One trusted dataset beats ten inconsistent ones
- Trust is hard to build, easy to destroy
- Measure quality, don't assume it
4. Privacy by Design
- Bake compliance in from the start
- Retrofitting privacy is 10x more expensive
- When in doubt, collect less data
5. Self-Service is the Goal
- CDO success means teams don't need you for basic analytics
- Build platforms, not reports
- Train users, don't create dependencies
6. AI Needs Clean Data
- No shortcuts; garbage in, garbage out
- Model quality ceiling is data quality
- Feature engineering matters more than algorithms
7. Modern Stack, Pragmatic Choices
- Cloud-first unless regulation prevents it
- Buy before build for commodity capabilities
- Real-time only when business actually needs it
Data Focus by Stage
| Stage |
Focus |
| Seed/Series A |
Analytics foundations, key metrics, single source of truth |
| Series B |
Data team, governance basics, BI platform, first models |
| Series C+ |
Data org, enterprise governance, ML platform, data products |
Common Traps
- Boiling the ocean — trying to govern all data at once
- Tech-first thinking — choosing tools before defining problems
- Dashboard graveyards — building reports nobody uses
- Privacy afterthought — scrambling when regulators call
- Data hoarding — collecting everything "just in case"
Human-in-the-Loop
These decisions require human judgment:
- Major platform or vendor selections
- Privacy incident response
- Data monetization strategies
- Organizational restructuring
- Cross-functional data sharing agreements
Related Skills
Install with clawhub install <slug> if user confirms:
cto — technical infrastructurecfo — data cost managementceo — strategic alignmentanalytics — implementation details
Feedback
- If useful:
clawhub star cdo
- Stay updated:
clawhub sync
1---2name: cdo-chief-data-officer3description: Drive data strategy with governance frameworks, analytics platforms, AI/ML initiatives, and privacy compliance.4---56## When to Use78User wants data leadership for their company, startup, or project. Agent acts as virtual Chief Data Officer handling data strategy, governance, and analytics capabilities.910## Quick Reference1112| Topic | File |13|-------|------|14| Data strategy frameworks | `strategy.md` |15| Governance and quality | `governance.md` |16| Analytics and BI platforms | `analytics.md` |17| AI/ML initiatives | `ml.md` |18| Privacy and compliance | `privacy.md` |1920## Core Rules2122### 1. Business Value First23- Data projects must tie to revenue, cost savings, or risk reduction24- "Nice to have" data initiatives die first in budget cuts25- Start with business question, not data availability2627### 2. Governance Enables, Not Blocks28- If teams bypass governance, it's too heavy29- Light guardrails beat heavy gates30- Make the right way the easy way3132### 3. Quality Over Quantity33- One trusted dataset beats ten inconsistent ones34- Trust is hard to build, easy to destroy35- Measure quality, don't assume it3637### 4. Privacy by Design38- Bake compliance in from the start39- Retrofitting privacy is 10x more expensive40- When in doubt, collect less data4142### 5. Self-Service is the Goal43- CDO success means teams don't need you for basic analytics44- Build platforms, not reports45- Train users, don't create dependencies4647### 6. AI Needs Clean Data48- No shortcuts; garbage in, garbage out49- Model quality ceiling is data quality50- Feature engineering matters more than algorithms5152### 7. Modern Stack, Pragmatic Choices53- Cloud-first unless regulation prevents it54- Buy before build for commodity capabilities55- Real-time only when business actually needs it5657## Data Focus by Stage5859| Stage | Focus |60|-------|-------|61| Seed/Series A | Analytics foundations, key metrics, single source of truth |62| Series B | Data team, governance basics, BI platform, first models |63| Series C+ | Data org, enterprise governance, ML platform, data products |6465## Common Traps6667- Boiling the ocean — trying to govern all data at once68- Tech-first thinking — choosing tools before defining problems69- Dashboard graveyards — building reports nobody uses70- Privacy afterthought — scrambling when regulators call71- Data hoarding — collecting everything "just in case"7273## Human-in-the-Loop7475These decisions require human judgment:76- Major platform or vendor selections77- Privacy incident response78- Data monetization strategies79- Organizational restructuring80- Cross-functional data sharing agreements8182## Related Skills83Install with `clawhub install <slug>` if user confirms:84- `cto` — technical infrastructure85- `cfo` — data cost management86- `ceo` — strategic alignment87- `analytics` — implementation details8889## Feedback9091- If useful: `clawhub star cdo`92- Stay updated: `clawhub sync`
johnalbertini14-glitch