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.

60

Quality

71%

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

92%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 lean, well-organized instruction-only skill with a clear sequenced workflow and built-in verification checkpoints. The only minor weakness is that the actionable guidance stays somewhat abstract rather than naming specific verification commands or methods.

DimensionReasoningScore

Conciseness

The ~13-line body is lean, assumes Claude's competence, and contains no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

The steps give concrete directional guidance ('Confirm current behavior with tests or reproduction', 'small, reviewable steps') but stay somewhat abstract for an instruction-only skill, with minor gaps in specific verification methods.

4 / 5

Workflow Clarity

Three clearly sequenced steps with verification baked in (confirm behavior up front, keep verification green at the end); as a simple single-purpose skill the workflow is unambiguous.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear sections (When to use, Non-goals, Workflow), matching the rubric's simple-skill exception for a top score.

5 / 5

Total

19

/

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 conveys a clear 'what' with a couple concrete actions but is missing an explicit 'Use when...' trigger clause and natural user-facing keywords, leaving the 'when' only weakly implied. It is moderately distinct but has non-trivial overlap with general refactoring skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to simplify, clean up, or reduce complexity in working code.'

Include natural user phrasings like 'simplify this', 'clean up this code', or 'reduce complexity' so it matches what users actually say.

Tighten the action list into a brief enumeration of concrete actions (e.g. 'reduce complexity, remove dead code, consolidate duplicated logic') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain (clarity, complexity, behavior preservation) and a couple concrete actions ('reduce needless complexity', 'preserve behavior', 'keep cleanup separate from correctness fixes'), but the action list is not comprehensive enough for a 4.

3 / 5

Completeness

The 'what' is clear, but the 'when' is only weakly implied by 'after behavior is understood' with no explicit 'Use when...' trigger, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Keywords like 'clarity' and 'complexity' are relevant but the description omits natural user phrasings ('simplify this', 'clean up this code') and has no explicit trigger clause.

3 / 5

Distinctiveness Conflict Risk

'Improve clarity / reduce complexity' is somewhat specific but overlaps broadly with general refactoring skills, so it could still trigger for the wrong skill.

3 / 5

Total

12

/

20

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.