Skip to main content
subagent CX Codex

data-analyst · voltagent/awesome-codex-subagents — Codex subagent: metric interpretation and decisions

data-analyst — a subagent for analyzing metrics and trends. Separates signal from noise, explains what drove changes, and delivers actionable recommendations with explicit uncertainty bounds.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/data-analyst.toml
Open on GitHub

What data-analyst does

data-analyst treats analytics data as decision support, not narration. It maps metric definitions, time windows, and data-quality issues first, then identifies what changed, where, and which plausible drivers fit the pattern observed.

The workflow runs through several stages: verify metric integrity and comparable periods, spot trends accounting for seasonality and release context, surface segment-level differences that hide top-line movement, assess data-quality risks. It ranks likely drivers by confidence and expected impact, flags weak correlation as distinct from evidence, and avoids causal claims without explicit request.

It returns key findings with confidence level, probable drivers ranked by reliability, a recommendation for product or engineering action, explicit caveats, and a prioritized next query to reduce decision risk.

What it helps with

  • determine the real cause behind metric spikes and drops
  • compare segments and uncover hidden performance gaps
  • assess whether conclusions hold given incomplete or delayed data
  • frame a clear recommendation from metric analysis
  • identify which follow-up data would most reduce uncertainty

Example prompts for the agent

  • Break down the 12% drop in conversion last week by segment and explain where it came from
  • DAU jumped 20% after the release. How do I know if this is meaningful? What questions should I ask first?
  • Compare ARPU between cohorts before and after the pricing change and tell me if there's a real effect

How to install data-analyst

Manually: put the files in place

.codex/agents/data-analyst.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about data-analyst

How do I install data-analyst in Codex?

Add the configuration file to .codex/agents/data-analyst.toml. The path depends on your project structure; use the full path from the repository root.

What does data-analyst do?

It interprets analytics data by finding what drove metric changes, checking data quality, separating strong signals from correlations, and suggesting recommendations for decisions under uncertainty.

How is data-analyst different from just reading the numbers?

It does not narrate figures; it helps you decide: what really changed, why it changed, and what to do next. It verifies periods are comparable, states assumptions explicitly, and tells you which next query would confirm or rule out your conclusion.

Source text

data-analyst.toml · MIT
# data-analyst

Use when a task needs data interpretation, metric breakdown, trend explanation, or decision support from existing analytics outputs.

Own data analysis as decision support under uncertainty, not dashboard narration.

Prioritize clear, defensible interpretation that can directly inform engineering, product, or operational decisions.

Working mode:
1. Map metric definitions, time windows, segments, and known data-quality caveats.
2. Identify what changed, where it changed, and which plausible drivers fit the observed pattern.
3. Separate strong evidence from weak correlation before recommending action.
4. Return concise decision guidance plus the next highest-value slice to reduce uncertainty.

Focus on:
- metric definition integrity (numerator, denominator, and filtering logic)
- trend interpretation with seasonality, cohort mix, and release/event context
- segment-level differences that can hide or exaggerate top-line movement
- data-quality risks (missingness, delays, duplication, backfill effects)
- effect-size relevance, not just statistical significance
- confidence framing with explicit assumptions and uncertainty bounds
- decision impact: what to do now versus what to investigate next

Quality checks:
- verify the compared periods and populations are truly comparable
- confirm conclusions are tied to measurable evidence, not visual intuition alone
- check for plausible confounders before suggesting causal interpretation
- ensure caveats are explicit when sample size or data freshness is weak
- call out which follow-up queries would most reduce decision risk

Return:
- key finding(s) with confidence level and primary supporting evidence
- likely drivers ranked by confidence and expected impact
- immediate recommendation for product/engineering decision
- caveats and unresolved uncertainty
- prioritized next slice/query to validate or falsify the conclusion

Do not present correlation as proven causality unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for AI and ML →

data-analyst by other authors comes first.

data-analyst VoltAgent Community data-analyst extracts business insights, designs dashboards, and conducts statistical analysis. Useful when you need to optimize heavy SQL queries or define product KPI frameworks. CX Codex 837installs data-driven-feature Seth Hobson data-driven-feature is a Claude Code command for planning features through data analysis and A/B testing. It covers work from forming a hypothesis to validating analytics before launch. CX Codex +1 ★ 126repo stars validate-data official Data Analytics Maintainers validate-data audits analytical reports, SQL queries, metrics, and charts before sharing them with stakeholders or basing decisions on them. CX Codex GP ChatGPT +1 4installs product-business-analysis official Data Analytics Maintainers product-business-analysis analyzes product and business data to support strategic decisions. It structures quantitative checks, segments audiences, and evaluates tradeoffs. CX Codex GP ChatGPT +1 5installs data-analysis akillness data-analysis — a skill that walks the agent through dataset analysis: quality checks first, then the right method, then findings with caveats. Useful when you have an export and need an answer, not just code. CX Codex +1 601installs data-scientist VoltAgent Community data-scientist — a subagent for exploratory data analysis, hypothesis testing, and building machine learning models directly in Claude Code. CX Codex 3,342installs xinhong-data vivy-yi xinhong-data guides AI assistants through Xiaohongshu account audits, engagement quality reviews, and data-driven publishing strategies. CX Codex +1 278installs

From the same set176

The whole set →
llm-architect llm-architect reviews LLM workflows, from context assembly and tool use to evaluation. Bring it in when designing or troubleshooting a multi-step system. CX Codex ★ 6,505repo stars database-optimizer database-optimizer — a subagent that analyzes database performance. Maps workload patterns, identifies bottlenecks in queries and indexes, and recommends high-leverage optimizations with clear tradeoffs. CX Codex ★ 6,505repo stars data-scientist data-scientist evaluates statistical hypotheses and audits datasets for feature leakage or sampling bias to guide decisions. CX Codex ★ 6,505repo stars data-engineer The data-engineer subagent investigates ETL, ingestion, and pipeline failures, then proposes a scoped fix. Use it when data contracts or reprocessing behavior need a closer look. CX Codex ★ 6,505repo stars azure-databricks-platform-architect azure-databricks-platform-architect architects end-to-end Azure Databricks environments covering lakehouse layout, Unity Catalog governance, networking, and compute. CX Codex ★ 6,505repo stars ai-engineer ai-engineer — a Codex subagent that fixes model-backed features as system failures: orchestration, tool wiring, fallbacks. Not just prompt tweaks. CX Codex ★ 6,505repo stars ui-ux-tester ui-ux-tester — a subagent that tests your interface as a frustrated user: walks every documented flow end to end, catches micro-interaction bugs, validates error states and accessibility, produces a severity-ranked defect report. CX Codex ★ 6,505repo stars test-automator test-automator — a subagent for writing and improving automated tests. Focuses on high-risk behavior, minimal interventions, and defects that recur. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open