root-cause-analyzer
Systematic root cause identification skill with 5 Whys, fishbone diagrams, fault tree analysis, and hypothesis testing
Profile →npx skills add a5c-ai/babysitter --skill root-cause-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Root Cause Analyzer ## Overview The Root Cause Analyzer skill provides comprehensive capabilities for systematic root cause identification and verification. It supports multiple analysis methods including 5 Whys, Ishikawa diagrams, fault tree analysis, and statistical hypothesis testing. ## Capabilities - 5 Whys facilitation - Ishikawa (fishbone) diagram creation - Fault tree analysis (FTA) - Hypothesis formulation - Chi-square testing - Correlation analysis - Pareto chart generation - Root cause verification ## Used By Processes - SIX-005: Root Cause Analysis - QMS-005: FMEA Facilitation - CI-002: A3 Problem Solving ## Tools and Libraries - Cause analysis tools - Statistical testing libraries - Visualization platforms - Collaboration tools ## Usage ```yaml skill: root-cause-analyzer inputs: problem_statement: "25% increase in customer complaints for product X" analysis_method: "fishbone" # 5_whys | fishbone | fta | is_is_not data: defect_counts_by_category: materials: 45 methods: 23 machines: 67 manpower: 12 measurement: 8 environment: 5 hypothesis_to_test: "Machine wear is causing increased defects" outputs: - root_cause_diagram - potential_causes - verified_root_causes - paret
- Overview
- Capabilities
- Used By Processes
- Tools and Libraries
- Usage
- Analysis Methods
- 5 Whys
- Ishikawa (Fishbone) Categories
- Fault Tree Analysis
- Verification Techniques
- Integration Points
What does the root-cause-analyzer skill do?
Systematic root cause identification skill with 5 Whys, fishbone diagrams, fault tree analysis, and hypothesis testing
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill root-cause-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.