root-cause-analysis
Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate why something is not working; especially for complex or intermittent issues across multiple components. Applies the Five Whys method, hypothesis-driven testing, stack trace analysis, git blame/log evidence gathering, and causal chain documentation to isolate and confirm root causes before applying any fix.
Install with Tessl CLI
npx tessl i github:rohitg00/skillkit --skill root-cause-analysis93
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific methodologies (Five Whys, hypothesis-driven testing, stack trace analysis), comprehensive natural trigger terms users would actually say, explicit 'Use when...' guidance, and a clear distinctive focus on systematic root cause analysis rather than quick fixes. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Five Whys method, hypothesis-driven testing, stack trace analysis, git blame/log evidence gathering, and causal chain documentation.' Also specifies outcomes like 'isolate and confirm root causes before applying any fix.' | 3 / 3 |
Completeness | Clearly answers both what ('systematic root cause analysis through structured investigation phases') AND when ('Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate'). Includes explicit 'Use when...' clause with comprehensive triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'bug', 'crash', 'error', 'broken behavior', 'debug', 'troubleshoot', 'investigate', 'not working', 'intermittent issues'. These are exactly what users naturally say when encountering problems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on root cause analysis methodology rather than general debugging. The emphasis on 'systematic investigation phases', 'Five Whys', and 'not just treating symptoms' distinguishes it from simple bug-fixing or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent workflow clarity and actionability. The five-phase investigation process is well-structured with clear validation checkpoints and feedback loops. Minor verbosity in explanatory sections (common categories, what Five Whys is) could be trimmed since Claude already understands these concepts.
Suggestions
Trim the 'Common Root Cause Categories' section - Claude already knows these categories; consider removing or condensing to a brief reminder list
Remove explanatory framing like 'Ask "Why?" repeatedly to drill down to the root cause' - the example demonstrates this sufficiently
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some explanatory text that Claude would already understand (e.g., explaining what 'Five Whys' means, listing common root cause categories). The tables and templates add value but some sections could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable guidance including specific bash commands for evidence collection, a clear hypothesis table format, verification checklists, and a documentation template. The Five Whys example is concrete and illustrative. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with five clearly sequenced phases, explicit validation checkpoints (Phase 5 verification checklist), and feedback loops (rejected hypothesis → re-evaluate → new hypotheses). The 'Red Flags' section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of headers, tables, and code blocks. References to other skills at the end are one-level deep and clearly signaled. Content is appropriately structured for a skill of this complexity. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
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.