root-cause-analysis
Skill14 starsChanged 42 days agoLicence not identifiedView on GitHub
Root Cause Analysis (RCA) for engineering problems — systematic step-by-step framework identifying scientific principles, analyzing physical parameters, and deriving actionable insights. Use this skill when the user wants to find the root cause of a technical failure, perform RCA for an engineering issue, identify physical parameters causing a defect, or mentions 'root cause analysis', 'RCA', 'failure analysis', or 'technical troubleshooting'.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- nledford/engineering-review-boardtheir own version, first seen Nov 3, 2026
- azoghry-commits/Cognition-OStheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- aictrl-dev/skillstheir own version, first seen Oct 22, 2026
- realityforge/skillstheir own version, first seen Oct 20, 2026
- JacobStephens2/skillstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use observability, adversarial-review and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
MicrosoftSkilladversarial-review
Adversarial review of a system design from 6 critical perspectives -- SRE, security, staff engineer, finance, operator, and developer advocate. Produces a unified risk assessment. Use for INTERACTIVE on-demand reviews during a design conversation (/adversarial-review). For RECIPE-DRIVEN reviews (where prior step context is needed), use the systems-design-critic agent instead.
Also in 3 projects that use this
GoogleSkilldomain-modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Also in 4 projects that use this
- GoogleSkill
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
- MicrosoftSkill
handoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
- +3 more from google
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- itseffi/agentic-os★ 114same name
- microsoft/cat-agent-skills★ 101same name
- nledford/engineering-review-board★ 11same name
- microsoft/aibast-agents-library★ 8same name
- viacheslav-tronko/claude-code-harness★ 6same name
- saitarrun/Devforge-ai★ 4same name
- aictrl-dev/skills★ 3same name
- azoghry-commits/Cognition-OS★ 3same name
- JacobStephens2/skills★ 2same name
- JeffreyFerreiras/ai-skills★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- 76-standard-solutionsSkill
- business-function-analysisSkill
- cause-effect-chain-analysisSkill
- contradiction-solverSkill
- derivative-resourcesSkill
- feature-transferSkill
- function-analysis-advancedSkill
- function-analysisSkill
- function-interaction-analysisSkill
- function-oriented-searchSkill
- idealitySkill
- innovation-checklistSkill
- interactive-trimmingSkill
- mpv-analysisSkill
- patent-analyzerSkill
- perception-mappingSkill
- physical-contradictionsSkill
- problem-operatorSkill
- resource-analysisSkill
- root-conflict-analysisSkill
- smart-little-peopleSkill
- solutions-at-system-levelsSkill
- sustainability-assessmentSkill
- system-descriptionSkill
- system-operatorSkill
- trimmingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.