How do I install the Root Cause Pareto skill?

Run npx skillmds@latest add gulmezeren2-byte/root-cause-pareto in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Root Cause Pareto safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Root Cause Pareto?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Root Cause Pareto free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Root Cause Pareto?

gulmezeren2-byte (@gulmezeren2-byte) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Root Cause Pareto by gulmezeren2-byte

Name: Root Cause Pareto
Rating: 4.2 (5 reviews)
Author: gulmezeren2-byte

Root Cause Pareto

Build a decision-grade Pareto for downtime, defects, complaints or delays - with unit-of-measure discipline, category hygiene, exposure normalization and a follow-up metric. Use when the user mentions pareto analysis, kök neden, duruş analizi, downtime, arıza analizi, defect ranking, şikayet analizi, 80/20 analysis. Differentiator - treats the Pareto as the start of a causal investigation, not a bar chart deliverable.

File contents

Root-Cause Pareto

A Pareto chart is easy; a Pareto that survives challenge in a management meeting is not. The difference is four disciplines applied before the chart exists.

Workflow

Pick the unit of measure deliberately. Occurrences, minutes, or money - choose the one closest to the pain being managed and say why. Ranking breakdowns by count when one category costs 10x more minutes per event points the team at the wrong problem. When in doubt, show count and impact side by side.
Enforce category hygiene before counting:
- Categories must sit at one granularity level (no "Mechanical failure" next to "Sensor S-114 misaligned")
- "Other/Miscellaneous" must stay under ~15% of the total; if it is bigger, the categorization failed - split it before proceeding
- Merge synonyms and near-duplicates (free-text logs always contain them; list the merges made)
Normalize by exposure before comparing. Line A with 3 shifts will "lead" any raw ranking against Line B with 1 shift. Divide by machine-hours, orders, or units produced when comparing across lines, shifts, or periods - state the exposure base used.
Check stability. A Pareto from one bad week is an anecdote. Compare the ranking across at least two comparable periods; only categories that stay on top deserve investment. Note rank changes.
Rank, plot, and go one level deeper on the #1 category. Break the top category into its own sub-Pareto or apply 5-why prompts to its most frequent instances. The actionable cause is usually one level below the headline category.
Define the counter-metric. Before recommending an action, state which number should move, by roughly how much, and when to re-measure. A Pareto without a follow-up measurement is decoration.

Pitfalls to check explicitly

Unit mismatch (count vs duration vs cost) silently reordering priorities
Unnormalized cross-line comparisons
"Other" as the tallest bar
Categories mixing symptoms ("stopped") with causes ("no material")
Acting on unstable rankings from short windows

Output format

One sentence: unit of measure, exposure base, period, and total impact covered
The ranked table (category, impact, share, cumulative) - chart optional, table mandatory
Sub-analysis of the top category with candidate root causes
Recommended action + counter-metric + re-measure date
Data notes: merges performed, rows excluded, Other%

---name: root-cause-paretodescription: Build a decision-grade Pareto for downtime, defects, complaints or delays - with unit-of-measure discipline, category hygiene, exposure normalization and a follow-up metric. Use when the user mentions pareto analysis, kök neden, duruş analizi, downtime, arıza analizi, defect ranking, şikayet analizi, 80/20 analysis. Differentiator - treats the Pareto as the start of a causal investigation, not a bar chart deliverable.---# Root-Cause ParetoA Pareto chart is easy; a Pareto that survives challenge in a management meeting is not. The difference is four disciplines applied before the chart exists.## Workflow1. **Pick the unit of measure deliberately.** Occurrences, minutes, or money - choose the one closest to the pain being managed and say why. Ranking breakdowns by *count* when one category costs 10x more *minutes* per event points the team at the wrong problem. When in doubt, show count and impact side by side.2. **Enforce category hygiene before counting:** - Categories must sit at one granularity level (no "Mechanical failure" next to "Sensor S-114 misaligned") - "Other/Miscellaneous" must stay under ~15% of the total; if it is bigger, the categorization failed - split it before proceeding - Merge synonyms and near-duplicates (free-text logs always contain them; list the merges made)3. **Normalize by exposure before comparing.** Line A with 3 shifts will "lead" any raw ranking against Line B with 1 shift. Divide by machine-hours, orders, or units produced when comparing across lines, shifts, or periods - state the exposure base used.4. **Check stability.** A Pareto from one bad week is an anecdote. Compare the ranking across at least two comparable periods; only categories that stay on top deserve investment. Note rank changes.5. **Rank, plot, and go one level deeper on the #1 category.** Break the top category into its own sub-Pareto or apply 5-why prompts to its most frequent instances. The actionable cause is usually one level below the headline category.6. **Define the counter-metric.** Before recommending an action, state which number should move, by roughly how much, and when to re-measure. A Pareto without a follow-up measurement is decoration.## Pitfalls to check explicitly- Unit mismatch (count vs duration vs cost) silently reordering priorities- Unnormalized cross-line comparisons- "Other" as the tallest bar- Categories mixing symptoms ("stopped") with causes ("no material")- Acting on unstable rankings from short windows## Output format1. One sentence: unit of measure, exposure base, period, and total impact covered2. The ranked table (category, impact, share, cumulative) - chart optional, table mandatory3. Sub-analysis of the top category with candidate root causes4. Recommended action + counter-metric + re-measure date5. Data notes: merges performed, rows excluded, Other%

Frequently asked questions