CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-clean

Identify and safely remove dead code with test verification

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./internal/template/templates/.agents/skills/moai-clean/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A minimal, token-efficient dispatcher body that gives concrete harness-specific invocation paths. Its main weakness is the absence of any verification step despite routing to a code-deletion workflow, plus a two-hop indirection for harnesses without a skill loader.

Suggestions

Add a brief verification note in the dispatch instructions (e.g. confirm the moai `clean` workflow runs tests after removal and to stop on failure), since the body routes a destructive operation with no local checkpoint.

For the no-loader path, state what the mirrored moai SKILL.md routing will ask for, so the two-hop indirection does not hide required arguments or prerequisites.

DimensionReasoningScore

Conciseness

The body is three lean lines with zero padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

It gives concrete, executable instructions (invoke `Skill("moai")` with arguments `clean`, or read the exact path `~/.agents/skills/moai/SKILL.md`), but "follow its routing" delegates without stating accepted arguments or expected behavior.

4 / 5

Workflow Clarity

The single dispatch action is unambiguous with clear harness-specific branches, but the skill's purpose is removing code (destructive) and the body contains no validation or verification step, so the destructive-operation cap limits this to 3.

3 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled external reference and no bundle files exist, but the no-loader path involves two levels of indirection (this SKILL.md to the mirrored moai SKILL.md to its routing), a minor organization gap.

4 / 5

Total

16

/

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 states a clear, specific capability (dead code identification and removal with test verification) in third person, but it entirely lacks trigger guidance for when the skill should activate. Adding a "Use when..." clause with natural synonyms would address its main weakness.

Suggestions

Add a trigger clause, e.g. "Use when the user mentions dead code, unused or unreachable code, or asks to clean up / remove unused functions or variables."

Include natural synonyms such as "unused code", "unreachable code", and "code cleanup" so the description matches how users actually phrase the request.

Briefly state what "test verification" means here (e.g. runs the test suite after each removal) to make the safety mechanism concrete.

DimensionReasoningScore

Specificity

"Identify and safely remove dead code with test verification" names the domain plus two concrete actions (identify, remove) and a safety mechanism, but coverage is not comprehensive — no languages, scope, or verification method are mentioned.

3 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"dead code" is a phrase users would naturally say, but common variations and synonyms such as "unused code", "unreachable code", or "cleanup" are missing.

3 / 5

Distinctiveness Conflict Risk

"Dead code" removal is a fairly distinct niche with only minor overlap risk against general code-cleanup or refactoring skills, though no explicit trigger phrases further separate it.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

modu-ai/moai-adk

Path

internal/template/templates/.agents/skills/moai-clean/SKILL.md

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.