CtrlK
BlogDocsLog inGet started
Tessl Logo

cause-and-effect

Systematic Fishbone analysis exploring problem causes across six categories

52

Quality

57%

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/cause-and-effect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 body provides a clear, actionable Fishbone workflow with three strong worked examples and good section structure. The main weakness is mild verbosity from three near-redundant examples that could be consolidated.

Suggestions

Consolidate to one canonical full example plus one shorter contrasting example to reduce token cost without losing coverage.

Add a brief validation checkpoint in the steps (e.g. 'confirm each root cause is supported by at least one category branch') to strengthen the workflow loop.

Consider moving the worked examples into a referenced examples file to keep SKILL.md a lean overview and lift progressive_disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient prose, but the three full worked examples are lengthy and somewhat redundant; could be tightened to one canonical example plus a shorter second, matching the 3-anchor of 'mostly efficient but could be tightened'.

3 / 5

Actionability

Concrete numbered steps with per-category brainstorm prompts and three complete worked examples showing the exact output format; minor gaps (no explicit prioritization formula) keep it just below 5.

4 / 5

Workflow Clarity

Six clearly sequenced steps with a 'why' digging loop and priority/solution steps; not a destructive/batch operation so the validation cap does not apply, but lacks explicit validation checkpoints for confirming root causes, keeping it at 4.

4 / 5

Progressive Disclosure

Well-organized sections (Description, Usage, Variables, Steps, Examples, Notes) with no bundle files needed; the long examples arguably belong in a separate file, a minor organization gap below 5.

4 / 5

Total

15

/

20

Passed

Description

50%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 states what the skill does but lacks an explicit 'Use when' trigger clause, capping completeness at 3. Trigger-term coverage is adequate but misses common synonyms like Ishikawa and root-cause analysis.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when diagnosing root causes of a problem, performing Ishikawa/Fishbone analysis, or exploring why something is failing.'

Include natural synonyms users say — 'root cause analysis', 'Ishikawa diagram', 'why analysis' — to improve trigger matching.

Name a couple more concrete actions (e.g. 'identify root causes and prioritize solutions') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('Fishbone analysis', 'six categories') and a concrete action ('exploring problem causes'), but does not list multiple specific actions — closer to the 3-anchor ('names domain and 1-2 concrete actions') than 4.

3 / 5

Completeness

Has a clear 'what' (Fishbone analysis across six categories) but no 'Use when...' clause, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes 'Fishbone' and 'causes' but omits natural variations users say ('root cause analysis', 'Ishikawa', 'why analysis'); matches the 3-anchor of 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

'Fishbone analysis' and 'six categories' give it a fairly distinct niche with only minor overlap risk against general analysis skills; just above the 3-anchor.

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.

Validation15 / 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
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.