Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/root-cause-investigation

@9449d36
Run it yourself

Systematic investigation of metric changes and anomalies. Use when a metric unexpectedly changes, investigating business metric drops, explaining performance variations, or drilling into aggregated metric drivers.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/root-cause-investigation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈60 tokens for metadata: the name and description. ≈703 when used: this file. ≈2.1k more on demand in 3 files.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈240 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Root Cause Investigation

When to use

  • A key metric dropped (or spiked) unexpectedly and the team needs an explanation
  • Stakeholders are asking "why did X happen?" and need an evidence-based answer
  • A metric change has been observed but the team is unsure whether it's noise or signal
  • Preparing a post-mortem after an incident that affected business metrics
  • A trend change happened weeks ago and needs retrospective investigation

Process

  1. Validate the change — confirm the metric changed beyond normal variance using a z-score or simple comparison to the rolling average. If the change is within ±1.5 standard deviations, document it as within normal range and close. Use scripts/drilldown_analyzer.py --validate.
  2. Establish a timeline — plot the metric over time to pinpoint when the change started. A sudden step change suggests a specific event; a gradual drift suggests a structural shift.
  3. Decompose the metric — break the metric into its constituent parts (e.g., revenue = volume × price × mix). Determine which component is driving the change before drilling into dimensions.
  4. Drill down systematically — compare the metric before vs. after the change across available dimensions (geography, platform, channel, product category, user segment). Sort by absolute contribution to identify the primary driver. Use scripts/drilldown_analyzer.py --drilldown. See references/rca_framework.md for the structured approach.
  5. Test hypotheses — generate explicit hypotheses (volume drop, mix shift, per-unit quality change, data issue) and accept or reject each with evidence. Correlate the timeline with known events from references/hypothesis_testing_guide.md.
  6. Write the root cause report — document the primary driver (quantified share of impact), supporting evidence, rejected hypotheses, and tiered recommendations (immediate / short-term / long-term). Use assets/rca_report_template.md.

Inputs the skill needs

  • Metric name and historical values (at least 30 days before the change)
  • Granular data with dimensional breakdowns (geography, platform, segment, etc.)
  • The date or date range when the change was noticed
  • A change log or incident log for the same period (product releases, campaigns, outages)
  • The business context: what decisions depend on this metric

Output

  • scripts/drilldown_analyzer.py — validates the change, computes dimensional drill-downs, and ranks contributors by impact
  • references/rca_framework.md — structured five-step RCA method with decision rules
  • references/hypothesis_testing_guide.md — checklist of common root causes and how to test each
  • assets/rca_report_template.md — report template: what changed, when, primary driver, supporting evidence, timeline, recommendations

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a structured methodology and a local tool for investigating business metric anomalies. It is safe to use and contains no network operations, external dependencies, or sensitive data access.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/root-cause-investigation