CtrlK
BlogDocsLog inGet started
Tessl Logo

consolidate

Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.

49

Quality

53%

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

Quality

Content

57%

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 well-structured, lean workflow with a concrete backup command and clear sequencing, but it has minor redundancy between Process and Don'ts, an illustrative rather than executable move step, and lacks an explicit error-recovery feedback loop for destructive moves. Progressive disclosure is strong given the skill's size and organization.

Suggestions

Provide an executable `mv` command for the move step instead of only arrow notation, e.g. `mv <child>/ <parent>/<child>/`.

Add an explicit feedback loop after verification: if a moved skill's `SKILL.md` is missing/invalid or links are broken, restore from the timestamped backup and retry.

Trim redundancy by either removing Don'ts that verbatim restate Process steps or repurposing them as a distinct quick-reference checklist rather than restating the same guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the Don'ts section largely restates Process steps (e.g. "Never move skills without backing up first" repeats step 2, "Don't break documentation directory alignment" repeats step 5), so it could be tightened.

2 / 3

Actionability

It provides one fully executable command (the timestamped `cp -r` backup) and concrete frontmatter/path examples, but the core "move" step uses illustrative arrow notation (`web-search/` → `web-research/web-search/`) rather than an executable `mv` command, leaving a key detail incomplete.

2 / 3

Workflow Clarity

The seven steps are clearly sequenced with a confirm-before-changes checkpoint (step 1) and a verify-after checkpoint (step 6), but for a destructive/batch directory-moving operation there is no explicit validate→fix→retry feedback loop (e.g. restore from backup if verification fails), which caps this dimension at 2.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no external references, and is organized into clear sections (When to use, Process, Don'ts), so per the scoring notes well-organized sections earn a 3 without needing external file references.

3 / 3

Total

9

/

12

Passed

Description

50%

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 concise and states concrete actions in third person, but it relies on technical jargon, omits any explicit "Use when..." trigger clause, and only partially distinguishes itself from the broader sub-skill skill family. Completeness and trigger-term quality are the main weaknesses.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user has approved a sub-skill grouping and wants to apply it by moving skills into a parent bundle."

Replace jargon-heavy phrasing with natural terms users would say, such as "consolidate", "group", or "nest skills into a parent".

Include a distinguishing cue that separates this apply/consolidate action from the review/proposal step to reduce overlap with sibling sub-skill skills.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("moving user-specified skills into a parent bundle" and "timestamped backups of every modified directory"), matching the anchor that names domain and some actions but is not comprehensive; it stops short of listing the full set of actions (parent creation, verification, reporting) the body covers.

2 / 3

Completeness

It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 even though the "what" is well covered.

2 / 3

Trigger Term Quality

Relevant keywords like "sub-skill grouping", "parent bundle", and "moving skills" appear, but the phrasing is technical jargon rather than the natural terms a user would say (e.g. "consolidate", "group skills", "nest skills"), and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The niche (applying an approved sub-skill grouping with backups) is somewhat specific, but without explicit trigger guidance it could still overlap with sibling `sub-skill.*` skills such as review.

2 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.