CtrlK
BlogDocsLog inGet started
Tessl Logo

review

Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.

57

Quality

66%

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 ./packages/agent-core-v2/src/app/skillCatalog/builtin/sub-skill/review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is a concise, well-structured instruction-only skill with a clear sequenced process, concrete deliverables, and a useful example output format. Its main limitation is mild abstraction in the inventory-listing step and the absence of any verification checkpoint for the produced analysis.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding of concepts Claude already knows; the skill-design criteria and example output format earn their place, with only minor room to tighten the example block.

4 / 5

Actionability

Concrete sequenced guidance with a specific per-group deliverable list and an example output format; the "scan the configured skill roots" step is slightly abstract, leaving a minor gap versus fully executable instruction.

4 / 5

Workflow Clarity

A clear 6-step Process with concrete sub-bullets and an explicit stop boundary ("Do not edit any file"); the destructive/batch validation cap does not apply to this read-only proposal task, but there are no explicit validation checkpoints for the analysis itself.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections (When to use, Process, Criteria, Example output format), meeting the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

17

/

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 states what the skill does and its read-only boundary, but lacks an explicit trigger clause and the natural trigger terms (review/reorganize/audit) that users would actually say. It is distinguishable from its sibling consolidate skill but moderately generic in its action vocabulary.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases such as 'review, reorganize, or audit the skill inventory'.

Broaden the action vocabulary beyond analyze/recommend/propose (e.g. 'group', 'audit', 'reorganize') to improve trigger term coverage.

Surface the natural user phrases ('review', 'reorganize', 'audit') in the description rather than only in the body's When-to-use section.

DimensionReasoningScore

Specificity

Names the domain ("skill set", "sub-skill bundles") and a couple of overlapping actions ("Analyze", "recommend candidate groups", "proposes a plan"), but the actions are variations of the same propose/analyze motion rather than a comprehensive set.

3 / 5

Completeness

The "what" is clear (analyze and recommend consolidation candidates), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords ("skill set", "sub-skill bundles", "consolidate") but omits the natural phrases users would say ("review", "reorganize", "audit"), which only appear in the body, not the description.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (read-only proposal of sub-skill groupings) and the "Read-only — proposes a plan, does not move files" clause distinguishes it from the sibling consolidate skill, leaving only minor overlap risk.

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

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
MoonshotAI/kimi-code
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.