Manually trigger the cdd-code-simplifier agent to review and simplify code
62
52%
Does it follow best practices?
Impact
67%
1.52xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/simplify/SKILL.mdQuality
Discovery
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 too terse and lacks explicit trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill. It names the general domain but doesn't enumerate specific simplification actions or include natural user-facing keywords like 'refactor', 'clean up', or 'reduce complexity'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to simplify, refactor, or clean up existing code, or when code complexity needs to be reduced.'
Include natural trigger terms users would say: 'refactor', 'clean up code', 'reduce complexity', 'simplify functions', 'remove dead code'.
List specific concrete actions the skill performs, e.g., 'Extracts repeated logic into functions, removes dead code, reduces nesting depth, and simplifies conditional expressions.'
| Dimension | Reasoning | Score |
|---|---|---|
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., reduce complexity, extract functions, remove 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' hints at when but doesn't provide user-facing trigger scenarios. Per rubric, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'simplify code' and 'review', but misses common variations users might say such as 'refactor', 'clean up code', 'reduce complexity', 'code cleanup'. The term 'cdd-code-simplifier' is internal jargon. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'cdd-code-simplifier agent' adds some distinctiveness, but 'review and simplify code' is broad enough to overlap with general refactoring or code review skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 for triggering a code simplifier agent. Its main strengths are token efficiency and clear organization. The primary weakness is the lack of a concrete Task tool invocation example and missing error handling/validation steps for when the agent produces unexpected results or fails.
Suggestions
Add a concrete example of the Task tool invocation showing the exact call structure with subagent_type and prompt parameters.
Add a brief error handling step for when the agent fails or makes no changes (e.g., 'If the agent reports no simplifications needed, inform the user').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line serves a purpose—no unnecessary explanations of what code simplification is or how agents work. The examples section efficiently shows usage patterns. | 3 / 3 |
Actionability | Provides clear direction on using the Task tool with subagent_type and scope determination logic, but lacks a concrete executable example of the actual Task tool invocation (e.g., the exact JSON/call structure). The git commands are specific, which helps. | 2 / 3 |
Workflow Clarity | The workflow has a clear sequence (determine scope → run agent → review → ask about commit → summarize), but there's no validation or error handling for when the agent fails or produces no changes. For an operation that modifies code files, a feedback loop or validation step would strengthen this. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (task, scope determination, post-completion steps, examples). No need for external references given the scope. | 3 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
814cd52
Table of Contents
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.