Root Cause Analysis
Use this skill whenever the user asks to diagnose why something failed, find the root cause of an incident, conduct a post-mortem, analyze a problem or defect, distinguish symptoms from causes, or apply 5 Whys or Fishbone analysis. Trigger on phrases like "why did this happen", "root cause", "post-mortem", "5 whys", "fishbone", "what caused this", "diagnose the failure", "why did it fail", "underlying cause". Do NOT trigger for general problem solving (use business-os), refining existing plans (use idea-refiner), or content quality audits (use content-quality-auditor).
Install
npx skills add microsoft/cat-agent-skills --skill root-cause-analysisgit clone --depth 1 https://github.com/microsoft/cat-agent-skills.git /tmp/cat-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/cat-agent-skills/submissions/root-cause-analysis ~/.claude/skills/root-cause-analysisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Root Cause Analysis
Guide the user through structured problem diagnosis to move from observed symptoms to the true underlying cause, using repeatable techniques that prevent guessing or stopping at surface-level fixes.
## Instructions
1. **Lock the problem statement**
- State the exact symptom or failure in one sentence.
- Capture when it occurred, where, and who or what was affected.
- Do not allow vague wording like "it broke" or "performance is bad."
2. **Map the symptom chain**
- List every observed symptom as a fact, not a hypothesis.
- For each symptom, ask: "What could produce this?"
- Keep asking "why" at least three levels deep before proposing any cause.
3. **Apply 5 Whys**
- Start from the problem statement.
- Ask "why" repeatedly, recording each answer.
- Stop when you reach a cause that, if fixed, would prevent the symptom from recurring.
- If you reach a cause that is a contributing factor rather than a fixable origin, keep going.
- Load `references/rca-methods.md` if the problem is complex or the user asks for a specific technique.
4. **Build a Fishbone diagram**
- Categorize potential causes across: People, Process, Technology, Data, Environment, Management.
- For each category, list specific contributing factors backed by evidence the user can confirm.
- Do not invent facts; if a factor is uncertain, mark it as unverified.Details
- Skill name
root-cause-analysis- Repository
- microsoft/cat-agent-skills
- Path
submissions/root-cause-analysis/SKILL.md- License
- MIT
- Repo updated
- 15 November 2026
FAQ
What does the Root Cause Analysis skill do?
Use this skill whenever the user asks to diagnose why something failed, find the root cause of an incident, conduct a post-mortem, analyze a problem or defect, distinguish symptoms from causes, or apply 5 Whys or Fishbone analysis. Trigger on phrases like "why did this happen", "root cause", "post-mortem", "5 whys", "fishbone", "what caused this", "diagnose the failure", "why did it fail", "underlying cause". Do NOT trigger for general problem solving (use business-os), refining existing plans (use idea-refiner), or content quality audits (use content-quality-auditor).
How do I install the Root Cause Analysis skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add microsoft/cat-agent-skills --skill root-cause-analysis. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Root Cause Analysis popular?
It lives in microsoft/cat-agent-skills, which has 110 GitHub stars and 122 forks.
Related skills
3 Statements
110microsoft/cat-agent-skills
Completes existing income statement, balance sheet and cash flow templates while preserving layout, grounding historical inputs and linking forecast formulas with reconciliation checks. Use for "fill in a 3-statement template", "complete an IS/BS/CF framework", "populate my integrated financial model", "link statements in this template", or "finish the forecasts in my three-statement workbook". Do NOT use for blank-slate models or general workbook edits (use xlsx), DCF valuation (use dcf-valuation), or buyout modeling (use lbo-model).
Accessibility Pass
110microsoft/cat-agent-skills
Use this skill whenever the user asks to check, review, or fix the accessibility of a PowerPoint deck, Word document, HTML page, or Markdown file, and before handing over any deck or document this agent just generated, so it does not ship with missing alt text, untitled slides, or unreadable colour contrast.
Accessible Learning Materials
110microsoft/cat-agent-skills
Maintains instructionally equivalent, accessible variants of a set of learning materials — lessons, readings, slides, and handouts — with parity checks against the original learning goals and recorded approvals. Use when the user asks to "make these materials accessible", "audit this lesson set for accessibility", "create an accessible version of this reading", "check reading level and alt text", or "keep my accessible variants in sync". Do NOT use for individual student accommodation or support-plan decisions (IEP, EHCP, or local equivalent), and do NOT use for generic document formatting (us
Section Draft
110microsoft/cat-agent-skills
Write or revise the language for one planned CSR or 510(k) section - synopsis, efficacy, safety, discussion, device description - using only figures already in the cited fact map, each with its TLF or SAP citation. Use when the user asks "draft the Synopsis from our locked tables", "write up safety from Table 14.3.1", "give me a first pass at the discussion", "draft the device description for the 510(k)" or "tighten the wording of the Discussion section". Do NOT use for supplying a number not already in source_facts - use source-ingest instead. Do NOT use for verifying a draft's figures - use
Redlining Content
110microsoft/cat-agent-skills
Use when the user asks to redline, track changes, or compare differences in a file. Compares an uploaded .docx or .pdf against a provided .dotx/.docx template and returns a redlined .docx where every textual difference is a Word tracked change (insertion/deletion) authored by "Copilot Studio AI". No visual conversion — built directly on the template.
Section Plan
110microsoft/cat-agent-skills
Work out which sections a CSR or 510(k) requires, from the templates in config, check each one against the cited fact map, and name what is missing before a word is drafted. Use when the user asks "what do we still need before we can draft the CSR?", "which sections are ready to start?", "what's blocking the performance data section?", "do we have everything for the synopsis?" or "map our tables to the E3 structure". Do NOT use for writing section language - use section-draft instead. Do NOT use for cross-checking a finished draft - use consistency-check instead. Do NOT use for outlining gener
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.