CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify

Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.

54

Quality

61%

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 ./crates/tui/assets/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.

The body is concise and well-organized for a simple, single-purpose skill, but its workflow guidance stays at a directional level without concrete examples or an explicit error-recovery loop, capping actionability and workflow clarity at the middle band.

Suggestions

Add one concrete before/after simplification example so the actionability dimension has specific, executable guidance.

Add an explicit error-recovery step to the workflow (e.g. 'If verification fails, revert the last step and retry') to turn the implicit checkpoint into a real feedback loop.

Optionally show a concrete verification command (e.g. re-run the reproduction) rather than only stating 'keep verification green'.

DimensionReasoningScore

Conciseness

The body is extremely lean ('Use after behavior is understood and the user wants clarity or less complexity', 'Do not “simplify” by deleting necessary safety checks') with no explanation of concepts Claude already knows, matching the score-3 anchor of a lean, efficient body where every token earns its place.

3 / 3

Actionability

Steps like 'Confirm current behavior with tests or reproduction' and 'Reduce complexity in small, reviewable steps' give directional guidance, but there are no concrete examples of what a simplification looks like or specific commands, fitting the score-2 anchor of some concrete guidance that is incomplete.

2 / 3

Workflow Clarity

The three-step workflow is sequenced and includes verification ('Confirm current behavior with tests or reproduction', 'Keep behavior-preserving verification green'), but there is no explicit feedback loop describing what to do when verification goes red, matching the score-2 anchor of steps present with implicit checkpoints.

2 / 3

Progressive Disclosure

At under 50 lines with no external references needed, the body is organized into clearly signaled sections (When to use, Non-goals, Workflow), which per the scoring notes lets progressive disclosure score 3 on well-organized sections alone.

3 / 3

Total

10

/

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 states what the skill does in clear but abstract terms and gestures at a precondition ('after behavior is understood'), yet it lacks an explicit 'Use when...' trigger clause and natural trigger keywords, leaving it at the middle band across all dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause listing natural phrases users say, e.g. 'Use when the user asks to simplify, clean up, or reduce complexity in code whose behavior is already understood.'

Replace abstract verbs with at least one concrete capability example so the specificity dimension can reach 3.

Include common trigger terms like 'simplify', 'clean up', and 'refactor for readability' to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Phrases like 'Improve clarity', 'reduce needless complexity', 'preserve behavior', and 'keep cleanup separate from correctness fixes' name several actions, but they are abstract guiding principles rather than concrete operations (e.g. 'extract text', 'fill forms'), matching the score-2 anchor of naming a domain and some actions without being comprehensive.

2 / 3

Completeness

The 'what' is clearly stated ('Improve clarity and reduce needless complexity'), but the 'when' is only weakly implied via 'after behavior is understood' with no 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms 'clarity', 'complexity', 'cleanup', and 'correctness fixes' are somewhat natural, but common variations a user would actually say (e.g. 'simplify', 'clean up', 'refactor for readability') are absent, fitting the score-2 anchor of some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The framing around behavior preservation and separating cleanup from correctness fixes gives it a niche, but simplification/cleanup overlaps broadly with refactoring and readability skills, matching the score-2 anchor of being somewhat specific but still able to overlap with similar skills.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
Hmbown/CodeWhale
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.