New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Root Cause Pareto

by davila7 in davila7/claude-code-templates

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.

MITAuto-check passedDevelopment

Install Root Cause Pareto

skills CLI
$ npx skills add davila7/claude-code-templates --skill root-cause-pareto -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates root-cause-pareto --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/operations/root-cause-pareto .claude/skills/root-cause-pareto && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
root-cause-pareto
GitHub stars
33k
Token cost
~791 tokens
SKILL.md length
386 words
Files
1
Skills in repo
479
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 6 steps: Pick the unit of measure deliberately.… → Enforce category hygiene before counting → Normalize by exposure before comparing.… → …
  • The user mentions pareto analysis
  • SKILL.md covers Workflow, Pitfalls to check explicitly and Output format
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Root Cause Pareto is an agent skill from davila7/claude-code-templates. 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.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Root cause analysis and Database schema design. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • The user mentions pareto analysis
  • Şikayet analizi

Example prompts

  • “/root-cause-pareto”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Pick the unit of measure deliberately. Occurrences, minutes, or money - choose the one closest to the pain being managed and say why…
  2. Enforce category hygiene before counting
  3. Normalize by exposure before comparing. Line A with 3 shifts will "lead" any raw ranking against Line B with 1 shift. Divide by…
  4. Check stability. A Pareto from one bad week is an anecdote. Compare the ranking across at least two comparable periods; only categories…
  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…
  6. Define the counter-metric. Before recommending an action, state which number should move, by roughly how much, and when to re-measure. A…

What it can do on your machine

Read from SKILL.md and the folder at commit c0ca7da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Root Cause Pareto loads about 791 tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 386 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~791

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit c0ca7da, republished under its MIT licence (© davila7). 386 words, ~791 tokens.

Download SKILL.mdSave it as .claude/skills/root-cause-pareto/SKILL.md (or your agent's skills folder).
name
root-cause-pareto
description
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 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.
  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.
Show full SKILL.md (109 more words)Show less

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

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

Source: industrial-engineering-ai-skills by Eren Gulmez (MIT). The full method pack - entry skill, role agents, data-hygiene rules and artifact templates - lives there.

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in cli-tool/components/skills/operations/root-cause-pareto of davila7/claude-code-templates.

Open the folder on GitHubat commit c0ca7da

Compare with similar skills

Root Cause Pareto next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Root Cause Pareto compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Root Cause Pareto this skilldavila7/claude-code-templates33k—~791Automated safety check: PassMIT
Effect TSmattiacerutti/supernova185—~2.8kAutomated safety check: PassMIT
Swiftdata ArchitectureKartikLabhshetwar/better-shot2.4k2 repos~1.2kAutomated safety check: PassCustom licence
Walkthroughalexanderop/walkthrough141—~3.4kAutomated safety check: NotesNone
Light System DesignLight0305/Light-skills640—~3.6kAutomated safety check: PassMIT
Databuddy Internaldatabuddy-analytics/Databuddy1.2k—~11kAutomated safety check: NotesAGPL-3.0

Similar skills

  • Effect TS

    mattiacerutti/supernova

    Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source.

    185 GitHub stars~2.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Swiftdata Architecture

    KartikLabhshetwar/better-shot

    Deep dive into SwiftData design patterns and best practices.

    2.4k GitHub starsUsed in 2 repos~1.2k tokens
    DevelopmentAuto-check passed

  • Walkthrough

    alexanderop/walkthrough

    Generates a self-contained HTML file with an interactive, clickable Mermaid diagram (flowchart or ER diagram) that explains how a codebase feature, flow, architecture, or database schema works.

    141 GitHub stars~3.4k tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes

  • Light System Design

    Light0305/Light-skills

    Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.

    640 GitHub stars~3.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Databuddy Internal

    databuddy-analytics/Databuddy

    Work inside the Databuddy monorepo for internal implementation, debugging, review, and refactoring.

    1.2k GitHub stars~11k tokensUpdated today
    DevelopmentAuto-check: notes

  • Physicalai Train Working With Datasets

    open-edge-platform/physical-ai-studio

    Works with Physical AI Studio datasets and Lightning datamodules built on the LeRobot format.

    133 GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

More from davila7/claude-code-templates

All 479 skills in this repo

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Auto-check: notes

  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    33k GitHub starsUsed in 9 repos~2.8k tokens
    Auto-check passed

  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    33k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes

  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    33k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed

  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    33k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Categories

Questions about Root Cause Pareto

What does Root Cause Pareto do?

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. Root Cause Pareto is an agent skill from davila7/claude-code-templates. 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.

When should I use Root Cause Pareto?

Root Cause Pareto fits situations like: the user mentions pareto analysis; Şikayet analizi.

How do I install Root Cause Pareto in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill root-cause-pareto -a claude-code`. Or copy the skill folder (cli-tool/components/skills/operations/root-cause-pareto in davila7/claude-code-templates) into .claude/skills/root-cause-pareto in your project. Claude Code loads it when a task matches its description.

How do I install Root Cause Pareto in Codex?

Run `npx skills add davila7/claude-code-templates --skill root-cause-pareto -a codex`. Or copy the skill folder (cli-tool/components/skills/operations/root-cause-pareto in davila7/claude-code-templates) into .agents/skills/root-cause-pareto in your project. Codex loads it when a task matches its description.

Can I use Root Cause Pareto in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill root-cause-pareto -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/root-cause-pareto, .gemini/skills/root-cause-pareto, .github/skills/root-cause-pareto and .opencode/skills/root-cause-pareto in your project.

What does Root Cause Pareto need to run?

SKILL.md names no scripts, command-line tools or credentials: Root Cause Pareto is instructions for the agent only.

Does Root Cause Pareto access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Root Cause Pareto safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Root Cause Pareto use?

Root Cause Pareto is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Root Cause Pareto use?

About 791 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Root Cause Pareto?

Skills that share tags, products or a category with Root Cause Pareto: Effect TS (mattiacerutti/supernova, 185 stars), Swiftdata Architecture (KartikLabhshetwar/better-shot, 2.4k stars), Walkthrough (alexanderop/walkthrough, 141 stars) and Light System Design (Light0305/Light-skills, 640 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Root Cause Pareto?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,512 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 10, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.