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

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise instruction-only skill body with a clear workflow and a clean one-level-deep reference that exists. Actionability and workflow_clarity are strong but stop just short of fully executable checkpoints/output templates.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or over-explanation of concepts Claude already knows; every section (Constraints, When to use, Workflow) earns its place.	5 / 5
Actionability	Provides concrete, specific guidance (chain why questions 'stopping when further why steps would require guessing', named Fishbone categories), but as an instruction-only skill it lacks a concrete inline output template.	4 / 5
Workflow Clarity	A clear 6-step sequence with embedded guidance to flag open findings, but checkpoints are implicit rather than explicit validate-then-fix-then-retry loops.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep, clearly-signaled reference (references/022-root-cause-analysis.md), which exists and holds the detailed guidance; navigation is easy.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete techniques and provides explicit 'Use when' trigger guidance with natural phrasing. Slightly formal trigger language keeps trigger_term_quality just short of comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete techniques — 'Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification' — providing comprehensive coverage of specific actions.	5 / 5
Completeness	Explicitly answers both 'what' (the four named techniques) and 'when' via the 'Use when a framed problem needs root-cause investigation' clause plus concrete trigger conditions.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('find the root cause of a problem', 'Root Cause Analysis', 'maintainer directly asks'), but a few common synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear RCA niche with distinct technique-specific triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/022-root-cause-analysis/SKILL.md
Commit: f6dfc6f

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.