Menu

Individual skill

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.

cli-tool/components/skills/operations/root-cause-pareto/SKILL.md

Read pinned source

Source commit ad81bf053f80b626801decf425f501ba49983d98

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
33,186
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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

1. **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.