/install cdo
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 \x3Cslug> if user confirms:
cto— technical infrastructurecfo— data cost managementceo— strategic alignmentanalytics— implementation details
Feedback
- If useful:
clawhub star cdo - Stay updated:
clawhub sync
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install cdo - After installation, invoke the skill by name or use
/cdo - Provide required inputs per the skill's parameter spec and get structured output
What is CDO / Chief Data Officer?
Drive data strategy with governance frameworks, analytics platforms, AI/ML initiatives, and privacy compliance. It is an AI Agent Skill for Claude Code / OpenClaw, with 733 downloads so far.
How do I install CDO / Chief Data Officer?
Run "/install cdo" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is CDO / Chief Data Officer free?
Yes, CDO / Chief Data Officer is completely free (open-source). You can download, install and use it at no cost.
Which platforms does CDO / Chief Data Officer support?
CDO / Chief Data Officer is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).
Who created CDO / Chief Data Officer?
It is built and maintained by Iván (@ivangdavila); the current version is v1.0.1.