CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify

Manually trigger the cdd-code-simplifier agent to review and simplify code

70

1.52x
Quality

64%

Does it follow best practices?

Impact

67%

1.52x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/simplify/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 tight, actionable instruction set for delegating to a simplifier agent, with exact commands and a clear post-run checklist. Its only weaknesses are minor: a redundant opening line and the absence of a sample agent prompt or a rollback step if the changes are unsatisfactory.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, no padding — but the opening sentence ("...for clarity, consistency, and maintainability") duplicates the description and could be trimmed. That minor over-explanation fits the anchor 4 example rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Guidance is concrete and executable: exact subagent_type, exact commands ("git diff --name-only main...HEAD" or "git status"), a $ARGUMENTS placeholder, and invocation examples. It falls short of fully copy-paste ready because no example prompt for the agent itself is provided, keeping it at anchor 4 rather than 5; it is well above the pseudocode-level anchor 3.

4 / 5

Workflow Clarity

The sequence is clearly laid out — scope determination, running the agent, then a numbered post-agent checklist that includes "Review the changes made" as a checkpoint. It lacks an explicit feedback loop for the case where the changes are wrong (no revert/retry step), so it matches anchor 4 rather than the explicit-validation anchor 5.

4 / 5

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines with no external references needed; per the scoring notes, well-organized sections ("## Your Task", "## Examples") suffice. The body is appropriately split into task, scope rules, post-steps, and examples with no inlined content that belongs elsewhere.

5 / 5

Total

17

/

20

Passed

Description

50%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, concrete capability but is minimal: no 'when to use' guidance, sparse trigger vocabulary, and moderate overlap risk with code-review/refactoring skills. All dimensions land at the mid anchor because the description does one thing adequately and nothing more.

Suggestions

Add a 'Use when...' clause, e.g. "Use when the user asks to simplify, clean up, or refactor recently changed code" — this would lift completeness and trigger-term quality simultaneously.

Include natural synonyms users would say ("refactor", "clean up code") to improve trigger term coverage and distinctiveness.

Clarify what the simplification covers (e.g. "removes duplication, tightens naming, simplifies control flow") to raise specificity beyond two generic actions.

DimensionReasoningScore

Specificity

The description names the domain ("code") and two actions ("review and simplify") but goes no further, matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so score 4 is not reached.

3 / 5

Completeness

The 'what' is clear ("trigger the cdd-code-simplifier agent to review and simplify code") but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

"review and simplify code" includes some natural keywords users would say, but common variations like "refactor" or "clean up" are missing. Coverage is relevant but not broad enough for the good-keyword-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"review and simplify code" is somewhat specific but overlaps with code-review and refactoring skills; the agent name is distinctive but the trigger surface is broad. It sits at the 'could still overlap with similar skills' anchor rather than 'mostly distinct'.

3 / 5

Total

12

/

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
aaddrick/claude-desktop-debian
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.