CtrlK
BlogDocsLog inGet started
Tessl Logo

analyse-problem

Comprehensive A3 one-page problem analysis with root cause and action plan

51

Quality

56%

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/analyse-problem/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 a clear 7-step workflow, but it is token-heavy due to two duplicated full A3 examples and would benefit from offloading those examples into reference files for better progressive disclosure.

Suggestions

Reduce duplication by keeping one compact worked example inline and moving the full examples to a references file (e.g., examples.md) to improve both conciseness and progressive disclosure.

Add an explicit validation/review checkpoint (e.g., 'review the completed A3 with the problem owner before finalizing') to strengthen workflow clarity.

Trim the repeated ASCII template headers and decorative box borders to cut token cost without losing information.

DimensionReasoningScore

Conciseness

The body is dominated by two near-identical full ASCII A3 templates (~120 lines each), which heavily pad the document relative to the lean Steps guidance; this is noticeably verbose even though accurate.

2 / 5

Actionability

Provides a concrete 7-step structure, a full blank template, and two worked examples with specific guidance like 'use 5 Whys or Fishbone'; mostly actionable with minor gaps.

4 / 5

Workflow Clarity

A clear, numbered 7-step sequence is laid out; the skill is non-destructive so the validation cap does not apply, though explicit review/checkpoint steps are absent.

4 / 5

Progressive Disclosure

Single file with well-organized sections and no nested references, but large worked examples are inlined that could live in separate reference files; the >50-line file does not qualify for the simple-skill exception.

3 / 5

Total

13

/

20

Passed

Description

57%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 a distinct niche (A3 problem analysis) but lacks an explicit trigger/use-when clause and only lists a couple of concrete actions. It is clearly distinguishable but stops short of comprehensive trigger-term coverage.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when analyzing incidents, recurring issues, or planning major improvements with a root cause and action plan').

Expand the concrete actions listed (e.g., 'conduct root cause analysis, define countermeasures, build an implementation plan') to raise specificity.

Add natural synonyms users would say ('5 whys', 'fishbone', 'incident', 'post-mortem') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the A3 problem-analysis domain plus two concrete outputs ('root cause', 'action plan'), but lists only 1-2 actions rather than a comprehensive set of specific capabilities.

3 / 5

Completeness

Has a clear 'what' (A3 one-page problem analysis with root cause and action plan) but no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes some natural terms a user would say ('problem analysis', 'root cause', 'action plan') but misses common synonyms and variations like '5 whys', 'fishbone', or 'incident'.

3 / 5

Distinctiveness Conflict Risk

The A3 framing with root cause and action plan is a distinct niche with specific triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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.