metric-diagnostics — Codex skill: what it does, how to install
This skill investigates metric changes, anomalies, gaps, and mismatches with expectations. Use it when you need evidence for likely drivers.
npx skills add openai/plugins --skill metric-diagnostics -a codexWhat metric-diagnostics does
The skill frames the diagnostic question before searching for causes. It clarifies the metric meaning, comparison window, population, grain, and owning source, then reproduces the calculation and measures the size, timing, and scope of the movement.
It searches relevant data surfaces, compares overlapping sources, and checks definitions, filters, joins, freshness, lineage, and aggregation. Driver analysis can use semantic layers, dashboards, tables, and other source-of-truth surfaces; fresh SQL or Python work can be recorded with jupyter-notebooks.
When a required source cannot be accessed, the skill stops that analysis path and asks for the source or a reviewed fallback. Related skills cover business context, data quality, and recommendations after the diagnosis.
What it helps with
- explain why a metric moved
- reproduce a comparison against a baseline
- rank the segments driving a change
- reconcile a gap between data sources
- test whether a spike reflects data-quality issues
Example prompts for the agent
- Diagnose why conversion changed between the two periods and quantify the segment contributions.
- Investigate the mismatch between the dashboard metric and the source table.
- Analyze the error spike: locate its onset, affected slices, and verified drivers.
How to install metric-diagnostics
1Skills CLI (Vercel)
npx skills add openai/plugins --skill metric-diagnostics -a codex2Manually: put the files in place
.agents/skills/metric-diagnostics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill metric-diagnostics -a claude-code2Manually: put the files in place
~/.claude/skills/metric-diagnostics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/metric-diagnostics/
Manually: put the files in place
.cursor/skills/metric-diagnostics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins metric-diagnostics2Manually: put the files in place
.github/skills/metric-diagnostics/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/data-analytics/skills/metric-diagnosticsManually: put the files in place
.devin/skills/metric-diagnostics/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: Codex skills: how to install, where they live, how to call them
Questions about metric-diagnostics
How do I install metric-diagnostics in Codex?
Run npx skills add openai/plugins --skill metric-diagnostics, then npx skills add openai/plugins --skill metric-diagnostics -a codex. The skill file is placed at .agents/skills/metric-diagnostics/SKILL.md.
What does metric-diagnostics do?
It reconstructs the metric, defines a valid comparison, measures the movement, and tests likely drivers across relevant cuts and data sources.
What happens when the required metric source is unavailable?
The skill stops that analysis path and asks for the required source or a reviewed fallback. A weaker substitute is not treated as equivalent.