CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify

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

62

1.52x
Quality

52%

Does it follow best practices?

Impact

67%

1.52x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/simplify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a concise, well-structured skill that clearly communicates the intent and basic workflow for triggering the code simplifier agent. Its main weaknesses are the lack of a concrete Task tool invocation example and missing error handling/validation steps for when the agent produces unexpected results. The examples section effectively shows user-facing usage patterns.

Suggestions

Add a concrete example of the actual Task tool invocation with the expected parameters/structure, so Claude knows exactly how to call it.

Add error handling guidance: what to do if the agent returns no changes, fails, or makes changes that break tests (e.g., run tests after simplification before offering to commit).

DimensionReasoningScore

Conciseness

The skill is lean and efficient. Every section serves a purpose—task definition, scope determination logic, post-completion steps, and usage examples. No unnecessary explanations of what code simplification is or how agents work.

3 / 3

Actionability

Provides clear guidance on using the Task tool with `subagent_type: "cdd-code-simplifier"` and gives concrete git commands for scope determination, but lacks an executable example of the actual Task tool invocation (e.g., the exact JSON/call structure). The examples section shows user commands, not Claude's execution steps.

2 / 3

Workflow Clarity

The workflow has a clear sequence (determine scope → run agent → review → ask about commit → summarize), but lacks validation checkpoints. There's no guidance on what to do if the agent fails, produces no changes, or makes problematic simplifications—no feedback loop for error recovery.

2 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (task, scope determination, post-completion steps, examples). No bundle files are needed.

3 / 3

Total

10

/

12

Passed

Description

32%

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 minimal and focuses on invocation mechanics ('manually trigger') rather than clearly communicating capabilities and usage triggers. It lacks a 'Use when...' clause, specific simplification actions, and natural user-facing trigger terms like 'refactor' or 'clean up'. The reference to an internal agent name adds little value for skill selection.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms like 'simplify code', 'refactor', 'reduce complexity', 'clean up code', 'code cleanup'.

List specific concrete actions the skill performs, such as 'extracts helper functions, removes dead code, reduces nesting depth, simplifies conditional logic'.

Remove implementation details like 'manually trigger the cdd-code-simplifier agent' and instead focus on what the skill accomplishes from the user's perspective.

DimensionReasoningScore

Specificity

Names the domain (code simplification) and a couple of actions (review and simplify code), but lacks detail on what specific simplification actions are performed (e.g., reducing complexity, extracting functions, removing dead code).

2 / 3

Completeness

Describes what it does (review and simplify code) but has no explicit 'Use when...' clause or equivalent trigger guidance. The word 'manually trigger' describes invocation mechanics rather than when to use it. Per rubric, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.

1 / 3

Trigger Term Quality

Includes relevant terms like 'simplify code' and 'review' which users might say, but misses common variations like 'refactor', 'clean up code', 'reduce complexity', 'code cleanup'. The term 'cdd-code-simplifier' is internal jargon unlikely to be used by users.

2 / 3

Distinctiveness Conflict Risk

The mention of 'cdd-code-simplifier agent' provides some distinctiveness as a specific named tool, but 'review and simplify code' is broad enough to overlap with general refactoring or code review skills.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

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.