CDO / Chief Data Officer

v1.0.1

Drive data strategy with governance frameworks, analytics platforms, AI/ML initiatives, and privacy compliance.

2· 702·0 current·0 all-time
byIván@ivangdavila
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description (data strategy, governance, analytics, ML, privacy) match the included SKILL.md and the five supporting files (strategy.md, governance.md, analytics.md, ml.md, privacy.md). All required content is proportional to a Chief Data Officer advisory skill; there are no unrelated requirements (no cloud creds, no unrelated binaries).
Instruction Scope
The runtime instructions ask the agent to act as a virtual CDO and point to topical guidance in the included files. The instructions do not direct the agent to read system files, environment variables, or external endpoints beyond optional use of the platform's 'clawhub install' when the user explicitly confirms. High‑risk actions (vendor selection, incident response, data monetization) are explicitly marked as human-in-the-loop.
Install Mechanism
There is no install spec and no code files; this instruction-only skill writes nothing to disk and does not download or execute third-party packages. That minimizes its install-time risk.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. SKILL.md does not attempt to access undeclared secrets. The lack of requested credentials is proportionate to a purely advisory skill.
Persistence & Privilege
always:false (default) and user-invocable:true. The skill does not request permanent presence or elevated platform privileges. Note: autonomous invocation (disable-model-invocation:false) is the platform default; this skill being able to be called autonomously is normal and not, by itself, a red flag.
Assessment
This skill is advisory-only and coherent with its purpose. Before installing or using it: (1) remember it does not request credentials, but any recommendations it gives may lead you to grant access to data systems — review and approve such access yourself; (2) treat vendor/tool recommendations as starting points, verify vendor trust and licensing before onboarding; (3) decline or carefully vet any follow-up prompts that ask you to paste secrets, run shell commands, or install third-party packages; (4) keep the human-in-the-loop items (incident response, vendor selection, data monetization) under direct human control rather than relying solely on the agent.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📊 Clawdis
OSLinux · macOS · Windows
latestvk97a9b7mmvq6y539rd5r7yxg7181h260
702downloads
2stars
2versions
Updated 1mo ago
v1.0.1
MIT-0
Linux, macOS, Windows

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

TopicFile
Data strategy frameworksstrategy.md
Governance and qualitygovernance.md
Analytics and BI platformsanalytics.md
AI/ML initiativesml.md
Privacy and complianceprivacy.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

StageFocus
Seed/Series AAnalytics foundations, key metrics, single source of truth
Series BData 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 infrastructure
  • cfo — data cost management
  • ceo — strategic alignment
  • analytics — implementation details

Feedback

  • If useful: clawhub star cdo
  • Stay updated: clawhub sync

Comments

Loading comments...