CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

why

Iterative Five Whys root cause analysis drilling from symptoms to fundamentals

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/kaizen/skills/why/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The content is well-structured and actionable with concrete worked examples and a clear validated workflow. The main weakness is minor redundancy in the Notes section that slightly hurts token efficiency.

Suggestions

De-duplicate the Notes section: 'Multiple root causes may exist - explore different branches' (line 91) and 'Multiple root causes are common-explore branches separately' (line 96) repeat, as do 'Document each why' notes (lines 92 and 98).

Consolidate the Notes into a tighter checklist to remove overlapping bullets and improve conciseness.

DimensionReasoningScore

Conciseness

The body is mostly lean with compact steps and examples, but the Notes section duplicates guidance ('Multiple root causes may exist' and 'Document each why' each appear twice), which could be tightened.

3 / 5

Actionability

Provides a concrete numbered process and three fully worked examples in a consistent 'Why 1-5 -> Root Cause -> Solution' format that is directly followable, with only minor gaps.

4 / 5

Workflow Clarity

Steps are clearly sequenced and include an explicit validation checkpoint (step 5: 'Validate by working backwards: root cause -> symptom'); only minor checkpoint gaps remain.

4 / 5

Progressive Disclosure

A simple single-purpose skill under 50 lines with no need for external references, organized into clear sections (Description, Usage, Variables, Steps, Examples, Notes), which meets the simple-skill bar for a 5.

5 / 5

Total

16

/

20

Passed

Description

53%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.

The description clearly identifies the skill's domain and method but lacks an explicit 'Use when...' trigger clause and richer action/synonym coverage, capping several dimensions at 3. It is reasonably distinct from other skills.

Suggestions

Add an explicit 'Use when...' clause naming the triggering situations, e.g. 'Use when investigating recurring issues, post-incident root cause analysis, or when the user asks why something happened.'

Expand trigger term coverage with natural synonyms such as 'RCA', 'postmortem', 'debugging why', and 'incident analysis'.

List a couple more concrete actions (e.g. 'documents each why, validates root cause by working backwards, proposes systemic fixes') to lift specificity to 4-5.

DimensionReasoningScore

Specificity

Names the domain ('Five Whys root cause analysis') and one concrete action ('drilling from symptoms to fundamentals'), but does not list several specific actions as required for a 4.

3 / 5

Completeness

Gives a clear 'what' (Five Whys root cause analysis) but no explicit 'when/Use when' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms like 'Five Whys', 'root cause analysis', and 'symptoms', but misses common synonyms and variations a user might say (e.g. RCA, 'why did this break', debugging).

3 / 5

Distinctiveness Conflict Risk

'Five Whys root cause analysis' is a specific niche with a distinct trigger phrase and minimal overlap risk with only closely related debugging/diagnostic skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/kaizen/skills/why/SKILL.md

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.