Keeper Stress Analysis
ClickHouse/ClickHouse
Analyze ClickHouse Keeper stress-test results from play.clickhouse.com / keeperstresstests data warehouse.
/cs:cdo-review <plan — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring.
Install Cdo Review
$ npx skills add alirezarezvani/claude-skills --skill cdo-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills cdo-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-agents/skills/cdo-review .claude/skills/cdo-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cdo-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review into .claude/skills/cdo-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cdo-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill cdo-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills cdo-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-agents/skills/cdo-review .agents/skills/cdo-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cdo-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review into .agents/skills/cdo-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cdo-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill cdo-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills cdo-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-agents/skills/cdo-review .cursor/skills/cdo-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cdo-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review into .cursor/skills/cdo-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cdo-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path c-level-agents/skills/cdo-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill cdo-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills cdo-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-agents/skills/cdo-review .gemini/skills/cdo-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cdo-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review into .gemini/skills/cdo-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cdo-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills cdo-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill cdo-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-agents/skills/cdo-review .github/skills/cdo-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cdo-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review into .github/skills/cdo-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cdo-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill cdo-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills cdo-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-agents/skills/cdo-review .opencode/skills/cdo-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cdo-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review into .opencode/skills/cdo-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cdo-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cdo-review- GitHub stars
- 28k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 433 words
- Files
- 1
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
/cs:cdo-review <plan — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring.
- Works in 6 steps: What decision does this data drive? → What's the consent provenance for every… → Who consumes this internally — and how… → …
- Validating training-data rights before model work
- SKILL.md covers When to Run, The Six CDO Questions, Workflow and Output Format, plus 2 more sections
- Calls python
What it does
Cdo Review is an agent skill from alirezarezvani/claude-skills. /cs:cdo-review <plan — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring. Use when validating training-data rights before model work, choosing warehouse vs lakehouse vs mesh, or valuing data assets for productization or M&A.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Data warehousing. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Validating training-data rights before model work
- Choosing warehouse vs lakehouse vs mesh
- Valuing data assets for productization
Example prompts
- “/cdo-review”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- What decision does this data drive?
- What's the consent provenance for every source?
- Who consumes this internally — and how many distinct functional domains?
- What's the M&A diligence impact?
- Can the model / decision / report be retrained / re-run / re-published without this source?
- What role unblocks this — and is it the right next hire?
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cdo Review loads about 1.3k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 433 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 433 words, ~1,280 tokens.
Download SKILL.mdSave it as
.claude/skills/cdo-review/SKILL.md (or your agent's skills folder).- name
- cdo-review
- description
- /cs:cdo-review <plan> — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring. Use when validating training-data rights before model work, choosing warehouse vs lakehouse vs mesh, or valuing data assets for productization or M&A.
/cs:cdo-review — CDO Forcing Questions
Command: /cs:cdo-review <plan>
The 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.
When to Run
- Before approving any new ML model training run that uses customer data
- Before signing a multi-year data-infrastructure SaaS contract (Snowflake, Databricks, Fivetran)
- Before productizing any customer data (benchmark report, embedding endpoint, license)
- Before a major data team hire (head of data, CDO, data PM, ML engineer)
- Before M&A diligence — yours or theirs
- When the founder uses the word "monetize" near "data"
The Six CDO Questions
1. What decision does this data drive?
If no decision is unblocked, why are we collecting / training on / productizing it?
- "We might need it later" is not a decision.
- "It feels like a moat" is not a decision.
- A real answer names a specific business call that requires this data.
2. What's the consent provenance for every source?
For each data source: origin, consent flow, data class, intended use.
- 1st-party-TOS-only is weaker than 1st-party-explicit-opt-in.
- Bundled TOS doesn't cover material new purposes (training on PII for foundation models).
- Run
ai_training_data_audit.pyif there's any AI use case in scope.
3. Who consumes this internally — and how many distinct functional domains?
Drives the centralize-vs-embed and warehouse-vs-mesh decisions.
- <5 consumers: warehouse-only.
- 5-25 consumers: lakehouse.
- 25+ consumers + federated culture: mesh.
- Premature architecture choice is the #1 cause of data-team burnout.
4. What's the M&A diligence impact?
If an acquirer asks about this data corpus tomorrow, are we ready?
- Is there a documented anonymization process?
- What % of customers have MSA carve-outs?
- Are training-data provenance logs current?
- Run
data_asset_valuator.pyquarterly.
Show full SKILL.md (157 more words)Show less
5. Can the model / decision / report be retrained / re-run / re-published without this source?
Tests how much you depend on a specific data source.
- If yes → low blast radius; you can change consent posture later.
- If no → high blast radius; you've structurally committed to the source. Vet harder.
6. What role unblocks this — and is it the right next hire?
Wrong hire (data scientist) when right answer (analytics engineer) is a 12-month productivity loss.
- Map the decision being unblocked to the specific role.
- Confirm prerequisite roles are in place (data engineer before ML engineer, analyst before data scientist).
Workflow
# 1. AI training audit (if any ML / AI use case)
python ../../../c-level-advisor/skills/chief-data-officer-advisor/scripts/ai_training_data_audit.py sources.json
# 2. Architecture decision (if changing the stack)
python ../../../c-level-advisor/skills/chief-data-officer-advisor/scripts/data_product_strategy_picker.py profile.json
# 3. Data asset valuation (if productizing or pre-M&A)
python ../../../c-level-advisor/skills/chief-data-officer-advisor/scripts/data_asset_valuator.py corpus.jsonOutput Format
# CDO Review: <plan>
**Date:** YYYY-MM-DD
## The Decision Being Made
[one sentence — which of the four CDO decisions: training | architecture | asset | hire]
## Training Audit (if applicable)
- NO-GO sources: N
- MITIGATE sources: N
- GO sources: N
- Top remediation: <one line>
## Architecture (if applicable)
- Recommended: WAREHOUSE / LAKEHOUSE / MESH
- Build-vs-buy summary: <one line>
- Kill criteria: <when to revisit>
## Asset Value (if applicable)
- Strategic value: X/10 | Moat: STRONG / MEDIUM / WEAK
- M&A multiplier: X.Xx – X.Xx ARR
- Recommended productization path: <name>
## Org (if applicable)
- Next hire: <role>
- Why this, not that: <one line>
- Prerequisite hires in place: yes/no
## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK
## Next Steps
[3 concrete actions]Routing
/cs:gc-review— for any productization or licensing path/cs:ciso-review— for any architecture change touching customer data/cs:cfo-review— for build-vs-buy TCO and M&A valuation mathcs-chro-advisoragent — for data team hires (comp, ladder, leveling)/cs:decide— log the verdict/cs:freeze 90— on multi-year infrastructure contracts
Related
- Agent:
cs-cdo-advisor - Skill:
chief-data-officer-advisor - Adjacent:
../../../c-level-advisor/skills/general-counsel-advisor/(contractual constraints),../../../c-level-advisor/skills/cto-advisor/(architecture capacity)
Version: 1.0.0
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in c-level-agents/skills/cdo-review of alirezarezvani/claude-skills.
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Cdo Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cdo Review this skillalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Keeper Stress AnalysisClickHouse/ClickHouse | 50k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 | |
| Perf ComparisonClickHouse/ClickHouse | 50k | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Patch Release CheckClickHouse/ClickHouse | 50k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Clickhouse Architecture Advisorvemetric/vemetric | 394 | 2 repos | ~791 | Automated safety check: Pass | Apache-2.0 | |
| Neocarta Add Source Connectorneo4j-labs/neocarta | 146 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Perf Comparison
ClickHouse/ClickHouse
Evaluate ClickHouse performance test results from existing CI/dashboard data or local perf.py runs.
Patch Release Check
ClickHouse/ClickHouse
Check whether ClickHouse's supported versions (last 3 majors + latest LTS) have recent stable patch releases, diagnose why the scheduled AutoReleases pipeline failed, and identify which releases…
Clickhouse Architecture Advisor
vemetric/vemetric
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs.
Neocarta Add Source Connector
neo4j-labs/neocarta
Scaffold, build, and verify a neocarta source or format connector against the connector contract.
Decompress Binary
ClickHouse/ClickHouse
Extract the inner ELF from a ClickHouse self-extracting clickhouse binary, including when its architecture differs from the host (e.g.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Cdo Review
What does Cdo Review do?
/cs:cdo-review <plan — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring. Cdo Review is an agent skill from alirezarezvani/claude-skills. /cs:cdo-review <plan — Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring.
When should I use Cdo Review?
Cdo Review fits situations like: validating training-data rights before model work; choosing warehouse vs lakehouse vs mesh; valuing data assets for productization.
How do I install Cdo Review in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill cdo-review -a claude-code`. Or copy the skill folder (c-level-agents/skills/cdo-review in alirezarezvani/claude-skills) into .claude/skills/cdo-review in your project. Claude Code loads it when a task matches its description.
How do I install Cdo Review in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill cdo-review -a codex`. Or copy the skill folder (c-level-agents/skills/cdo-review in alirezarezvani/claude-skills) into .agents/skills/cdo-review in your project. Codex loads it when a task matches its description.
Can I use Cdo Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill cdo-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cdo-review, .gemini/skills/cdo-review, .github/skills/cdo-review and .opencode/skills/cdo-review in your project.
What does Cdo Review need to run?
Going by SKILL.md and its folder, Cdo Review needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Cdo Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cdo Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cdo Review use?
Cdo Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cdo Review use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cdo Review?
Skills that share tags, products or a category with Cdo Review: Keeper Stress Analysis (ClickHouse/ClickHouse, 50k stars), Perf Comparison (ClickHouse/ClickHouse, 50k stars), Patch Release Check (ClickHouse/ClickHouse, 50k stars) and Clickhouse Architecture Advisor (vemetric/vemetric, 394 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cdo Review?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.