
Metric Diagnostics
Diagnose why a metric changed or differs from expectation.
Install
npx skills add XiaomiMiMo/MiMo-Code --skill metric-diagnostics -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,484 tokens
- Runs scripts
- No, instructions only
What it does
Diagnose why a metric changed or differs from expectation. Use when the task is to identify likely drivers of a metric movement, anomaly, gap, or discrepancy.
Related Skills
Use $gather-business-context when business context is needed to understand the metric, analysis period, ownership, or plausible explanations.
Use $product-business-analysis when the task asks for a recommendation or tradeoff decision after diagnosing the movement.
Use $analyze-data-quality when dashboard trust, grain, freshness, or source disagreement could affect the metric.
Metric Diagnostics
Use this skill to diagnose why a metric changed or differs from expectation. Reproduce the metric, define the comparison, quantify the movement, validate likely drivers, and state what is verified, likely, unresolved, and useful to do next.
Clarify with the user when a missing input would materially change the analytical frame or recommendation. Otherwise make a reasonable assumption, state it, and proceed.
Skill Configuration
Source Discovery And Verification
Use the relevant semantic layer as a starting map, not a boundary.
- Explore all possible sources. Search every connected or provided source that could contain task-relevant data or change the interpretation. Within each structured-data source, run fresh catalog or metadata discovery for relevant schemas, datasets, tables, views, models, and metrics. Known sources, tables, dashboards, and semantic mappings are starting points, not stopping points.
- Compare duplicates and conflicts. When sources overlap or disagree, compare ownership, freshness, definition, grain, coverage, and directness. Use the best authoritative source, or combine complementary sources when needed. Note material conflicts, explain why the selected source or sources control the answer, and verify selected data through live reads before concluding.
Source Access Guardrail
Before querying sources, building artifacts, or drawing conclusions, determine whether the answer requires a specific source of truth.
