CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

simplify-code

Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.

Quality

69%

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 ./.agents/skills/simplify-code/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable six-step workflow with concrete commands, defined output schemas, and explicit safety boundaries (no staging/committing, high-confidence fixes only). Its weaknesses are minor: some duplicated mode-trigger wording, no verbatim sub-agent prompts, and no explicit validation retry loop.

DimensionReasoningScore

Conciseness

The body is imperative and lean with no re-teaching of concepts Claude already knows; every step adds skill-specific guidance. Minor trimming is possible — the mode trigger words ("review", "audit", "check" / "simplify", "clean up", "refactor") are listed twice in the Modes section — so it matches anchor 4 rather than 5's "every token earns its place".

4 / 5

Actionability

Gives concrete commands ("git diff", "git diff --cached"), a defined finding schema (file, line, category, why, fix, confidence), per-role sub-agent checklists, and concrete fix and validation examples. It falls short of anchor 5 only because the sub-agent launch itself is described rather than given as copy-paste-ready prompts or commands.

4 / 5

Workflow Clarity

Six clearly sequenced steps with mode gating, explicit stop conditions ("If there is no clear scope, stop and say so briefly"; "In review-only mode, stop after reporting findings"), and a dedicated validation step with scoped examples. It misses anchor 5 because there is no explicit validate-fail-fix-retry feedback loop; the skill is not destructive or batch (it forbids staging/committing), so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~175-line body is organized into clear, well-ordered sections with nothing inlined that clearly belongs in a separate file. The four sub-agent role checklists could arguably be split into reference files, a minor organization gap that matches anchor 4 rather than 5's ideal overview-plus-references structure.

4 / 5

Total

16

/

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 pair (review a diff, apply low-risk fixes) in third person, but it omits any "when to use" trigger guidance and lacks the natural synonyms (simplify, clean up, refactor) users would most likely say. It is serviceable but sits at the midpoint on nearly every dimension.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to simplify, clean up, refactor, or review changed code or a diff."

Include the natural synonyms users say ("simplify", "clean up", "refactor", "code") alongside "diff" to broaden trigger-term coverage.

Mention the full review scope (reuse, quality, efficiency, clarity) so the description's capabilities match the body and it distinguishes itself from generic code-review skills.

DimensionReasoningScore

Specificity

Names two concrete actions ("Review a diff for clarity and safe simplifications", "optionally apply low-risk fixes") but coverage is not comprehensive — the body's reuse, quality, and efficiency review dimensions are absent from the description. It matches anchor 3 (domain plus 1-2 concrete actions) rather than 4, which requires several actions with only minor gaps.

3 / 5

Completeness

The "what" is clear (review a diff for clarity/safe simplifications, optionally apply low-risk fixes) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the "what" is concrete, not vague; not 4 because "when" is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Includes relevant keywords like "diff", "clarity", "simplifications", and "fixes", but misses the natural phrases users would actually say such as "simplify", "clean up", "refactor", or "code". This matches anchor 3 (some relevant keywords, missing common variations or synonyms) rather than 4, since more than a few natural terms are missing.

3 / 5

Distinctiveness Conflict Risk

"Review a diff" and "apply fixes" sit in crowded territory overlapping generic code-review and refactoring skills, so it could trigger for the wrong skill. Somewhat specific but real overlap risk remains, matching anchor 3 rather than 4's "minor overlap risk with closely related skills".

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.

Validation — 15 / 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

BigSimmo/Communication

Path

.agents/skills/simplify-code/SKILL.md

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.