root-cause-analysis SKILL.md skillA
root-cause-analysis from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/root-cause-analysis@git:20260323.771ca1cPins git:20260323.771ca1c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/business-analyst/root-cause-analysis/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260323.771ca1c, committed Mar 23, 2026
- Size
- 5,778 bytes
- Repository stars
- 21
- License
- MIT
Find the root cause of a problem, not just symptoms. Use when the user says "root cause", "why does this keep happening", "5 whys", "fishbone diagram", "cause analysis", "problem investigation", "defect analysis", "incident analysis", "A3 problem solving", "what's causing this", "ishikawa" - even if they don't explicitly say "root cause analysis".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Reference Files
- `references/fishbone-categories.md` - Six fishbone categories adapted for BA context (People, Process, Technology, Policy, Environment, Data) with example causes for each. Read this in Step 4 when building the Ishikawa diagram.
## Overview
Based on **Business Process Change** by Paul Harmon - integrating Six Sigma DMAIC root cause methodology into business process improvement. Also draws on **Lean Business Analysis** by Mark Sherrington for the A3 Problem Solving technique - a one-page structured format that forces clarity by constraining the entire analysis to a single sheet. The key insight: most "root causes" identified in practice are actually symptoms. True root cause analysis requires asking "why" until you reach a systemic cause you can change - something in the process, policy, or system design, never an individual person.
## Workflow
### Step 1: Write the problem statement
Be specific and measurable. A good problem statement answers: what, where, when, and how much.
```
BAD: "The system is slow."
GOOD: "Order processing takes 4.2 hours on average, exceeding the 2-hour SLA.
This has occurred for 67% of orders in the past 30 days, primarily
…Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/root-cause-analysis@sha256:5fa758d7913f547bThe line at the top of this page pins the label git:20260323.771ca1c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_izxspvn6izggh4xt)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 23, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5778 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_izxspvn6izggh4xt GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/root-cause-analysis GET https://markdownregistry.com/api/v1/blob/5fa758d7913f547b424536b394668b354f1b7760fa5f0f86ebd2ec0cbce40eb8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills