022 Root Cause Analysis logo

022 Root Cause Analysis

Community
jabrena
022-root-cause-analysis

Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the root cause of a problem before proposing a fix. Part of Plinth Toolkit

Overview

Publisherjabrena
Repositoryplinth
Skill name022-root-cause-analysis
Stars
455
Forks
95
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jabrena on GitHub. Read the source before you install it.

Installation

Install the 022 Root Cause Analysis AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/jabrena/plinth/tree/main/skills/022-root-cause-analysis
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jabrena/plinth.git /tmp/plinth
mkdir -p .claude/skills
cp -r /tmp/plinth/skills/022-root-cause-analysis .claude/skills/022-root-cause-analysis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 022 Root Cause Analysis in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 022 Root Cause Analysis on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 022 Root Cause Analysis is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Root Cause Analysis

Guide the identification of root causes, not symptoms, for a framed problem, using Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This is an interactive SKILL.

What is covered in this Skill?

  • Five Whys for a linear causal chain from a symptom to a root cause
  • Fishbone (Ishikawa) for categorized candidate causes across multiple dimensions
  • Current Reality Tree for interconnected causes and effects with a small number of core problems
  • Constraint identification for the limiting factor holding the current state in place
  • Choosing the technique(s) proportionate to the problem's complexity
  • Feeding root-cause findings into 023-assumption-analysis and the remaining Functional Specification lenses

Constraints

Distinguish root causes from symptoms before recommending a fix. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly.

  • MUST read references/022-root-cause-analysis.md before applying Root Cause Analysis guidance
  • MUST distinguish a symptom (an observed effect) from a root cause (the condition that produces it)
  • MUST apply Five Whys as a chain of "why" questions grounded in evidence from the problem frame, not assumption
  • MUST apply Fishbone to organize candidate causes into categories (for example people, process, technology, environment) when more than one causal dimension is plausible
  • MUST apply Current Reality Tree when multiple symptoms may share one or a small number of core problems connected by cause-effect relationships
  • MUST identify the constraint limiting the current state, not only the most visible cause
  • MUST NOT invent a root cause when the available evidence is vague or ambiguous; flag the gap for a clarifying question instead

When to use this skill

  • Find the root cause of this problem
  • Apply Five Whys to this issue
  • Build a Fishbone diagram for this problem
  • Use Current Reality Tree to connect these symptoms
  • Identify the constraint limiting the current state
  • Draft the Root Cause Analysis section of a Functional Specification

Workflow

  1. Read the Reference

Read references/022-root-cause-analysis.md, then identify the symptom(s) evidenced by the problem frame.

  1. Apply Five Whys

Chain "why" questions from the symptom toward an evidenced root cause, stopping when further "why" steps would require guessing.

  1. Apply Fishbone When Multiple Dimensions Are Plausible

Organize candidate causes into categories when more than one causal dimension (people, process, technology, environment) is plausible.

  1. Apply Current Reality Tree When Symptoms Interconnect

Connect multiple symptoms to a small number of shared core problems through cause-effect relationships when the symptoms appear related.

  1. Identify the Constraint

Name the constraint limiting the current state, distinct from the most visible or most recently reported cause.

  1. Report the Root Cause Findings

Report findings using Five Whys, Fishbone, Current Reality Tree, and the identified constraint, and flag any finding left open pending a clarifying answer.

Reference

For detailed guidance, examples, and constraints, see references/022-root-cause-analysis.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the 022 Root Cause Analysis AI skill do?

Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the root cause of a problem before proposing a fix. Part of Plinth Toolkit

Why use 022 Root Cause Analysis on TypingMind?

Because you install it once and use it with any model. 022 Root Cause Analysis is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 022 Root Cause Analysis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jabrena/plinth/tree/main/skills/022-root-cause-analysis. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use 022 Root Cause Analysis?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 022 Root Cause Analysis?

As many as you like. As long as a model supports skills, you can use 022 Root Cause Analysis with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 022 Root Cause Analysis AI skill free?

Yes. It is published on GitHub by jabrena under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇