CtrlK
BlogDocsLog inGet started
Tessl Logo

analyse

Auto-selects best Kaizen method (Gemba Walk, Value Stream, or Muda) for target

52

Quality

58%

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 ./antigravity/skills/analyse/SKILL.md

The canonical home for this skill is analyse in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 delivers concrete, actionable analysis methodology with clear per-method workflows and illustrative output templates. Its main weaknesses are verbosity from large inlined examples and repeated guidance, and the absence of any progressive-disclosure file structure to offload the long worked examples.

Suggestions

Move the long worked examples (auth gemba walk, CI/CD, feature VSM, incident VSM, API waste) into separate reference files (e.g., references/gemba-examples.md) and link to them from SKILL.md to improve conciseness and progressive disclosure.

De-duplicate the 'When to Use' criteria, which appear both in the Method Selection Logic section and again under each method; keep a single canonical decision list.

Trim or consolidate the Notes section, which restates selection guidance already covered in Method Selection Logic.

DimensionReasoningScore

Conciseness

The body is mostly efficient and domain-specific, but ~270 lines of worked examples plus redundant 'When to Use' blocks (repeated in both the selection-logic section and each method) and a Notes section that restates selection guidance could be tightened.

3 / 5

Actionability

Each method has a concrete numbered process and the worked examples double as copy-ready output templates; as an instruction skill the guidance is specific and executable, with only minor gaps.

4 / 5

Workflow Clarity

A clear top-level Steps sequence and a per-method Process with explicit phases; because the work is analysis (not destructive/batch), the validation cap does not apply, though explicit verification checkpoints are light.

4 / 5

Progressive Disclosure

Section structure is well organized, but there are no bundle files and the large worked examples are inlined in SKILL.md; content that could live one level deep in references is kept inline, so it is not a 5.

3 / 5

Total

14

/

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 is a concise, third-person statement that clearly identifies a distinct niche, but it lists only a single action and omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause with natural trigger terms would substantially raise completeness and trigger quality.

Suggestions

Append an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when analyzing a codebase, workflow, or process for inefficiencies').

Expand beyond the single 'Auto-selects' action to name the concrete outputs the skill produces (e.g., '...and guides you through the selected technique to produce actionable findings').

Add everyday synonyms alongside the jargon (e.g., 'waste analysis', 'process mapping', 'go-and-see review') so users trigger it with natural language.

DimensionReasoningScore

Specificity

Names the domain and three specific methods (Gemba Walk, Value Stream, Muda) but describes only one action ('Auto-selects'), so it is not a comprehensive list of concrete actions.

3 / 5

Completeness

It gives a clear 'what' (auto-selects a Kaizen method) but provides no 'Use when...' trigger clause, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Relevant domain keywords (Kaizen, Gemba Walk, Value Stream, Muda) are present, but they are specialized jargon missing the natural synonyms and variations a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The Kaizen/Lean analysis niche is distinct with method-specific triggers; only minor overlap risk with adjacent analysis skills keeps it just below 5.

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

skill_md_line_count

SKILL.md is long (510 lines); consider splitting into references/ and linking

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.