root-cause-pareto

Builds decision-grade Pareto analyses for downtime, defects, complaints, and delays.

30.5k|3.5k|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/davila7/claude-code-templates --skill root-cause-pareto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-cause-pareto
Source: https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/root-cause-pareto
Command: npx skills add https://github.com/davila7/claude-code-templates --skill root-cause-pareto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Raw Pareto charts often mislead teams because of unit-of-measure mismatches, messy categories, unnormalized comparisons, and unstable rankings. This Skill turns Pareto analysis into a disciplined root-cause investigation that survives scrutiny in management reviews.

Core Features & Use Cases

  • Unit-of-Measure Discipline: Chooses between occurrences, minutes, or cost based on the pain being managed, and shows count versus impact side by side.
  • Category Hygiene & Normalization: Enforces single-granularity categories, keeps "Other" under 15%, merges synonyms, and normalizes by exposure such as machine-hours or units produced.
  • Stability Checks & Follow-Up Metrics: Compares rankings across periods, drills into the top category with sub-Pareto or 5-why analysis, and defines a counter-metric with a re-measure date.
  • Use Case: A plant manager analyzing downtime across production lines gets a ranked table normalized by shift hours, a sub-analysis of the leading failure category, and a concrete action with a measurable target.

Quick Start

Analyze my downtime log with a Pareto analysis, normalize by machine-hours, and drill into the top category to find candidate root causes.

Frequently Asked Questions about root-cause-pareto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I do a Pareto analysis on downtime data?

Choose a unit of measure such as minutes or cost rather than raw counts, clean categories to one granularity level, normalize by exposure like machine-hours, then rank categories and drill into the top one with a sub-Pareto or 5-why analysis.

How to normalize Pareto analysis across production lines?

Divide each category's impact by an exposure base such as machine-hours, orders, or units produced before comparing lines or shifts. A line running three shifts will otherwise dominate any raw ranking against a single-shift line.

What is the difference between count-based and cost-based Pareto ranking?

Count-based ranking orders categories by occurrence frequency, while cost or duration ranking weights each event by its impact. A rare but expensive failure mode can be invisible in a count ranking, so showing both side by side prevents misdirected effort.

Why is my Pareto chart misleading in management reviews?

Common causes include an oversized Other category above 15 percent, mixed granularity levels, unnormalized cross-line comparisons, and rankings built from a single short period. Checking stability across at least two comparable periods filters out anecdotal rankings.

When should I not act on a Pareto analysis result?

Avoid acting when the ranking comes from one short time window, when categories mix symptoms with causes, or when the Other bucket is the tallest bar. Stabilize the categorization and confirm the ranking persists across periods before investing.