CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

simplify-code

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

Quality

74%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/simplify-code/SKILL.md

The canonical home for this skill is simplify-code in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

A well-structured, directive workflow with concrete commands, an explicit findings format, and clear mode gating, consistently scoring just below top marks across all dimensions. The main gaps are minor redundancy, implicit sub-agent launch details, and no explicit validation-failure recovery loop.

Suggestions

Consolidate the Modes section with the default-mode mapping to remove the duplicated keyword→mode listing, and state the recommended reviewer role once instead of per sub-agent.

Add one example sub-agent prompt or invocation to make the parallel-review step fully executable.

In Step 5, add a failure path: if validation fails, fix the introduced breakage or revert the fix and report it.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's competence throughout — e.g., "Do not assume `git diff HEAD` is the right default when a smaller diff is available" — with no explanation of concepts Claude already knows. Minor trimmable redundancy keeps it at anchor 4 rather than 5: the mode defaults are listed twice (Modes section plus the default mapping that repeats the same keyword→mode pairs), and "Recommended sub-agent role: `reviewer`" is repeated across three sub-agent sections.

4 / 5

Actionability

Guidance is concrete and executable: exact commands ("git diff", "git diff --cached"), an explicit findings schema (file, line/symbol, problem, fix, confidence high/medium/low), mode-selection rules, and concrete fix/validation examples. It falls short of anchor 5 because the sub-agent launch instructions are left implicit — no example prompt or spawn invocation is given — leaving a minor gap.

4 / 5

Workflow Clarity

Six steps are clearly sequenced with a scope-preference order, explicit stop conditions ("If there is no clear scope, stop"), mode-gated behavior, and a validation step with scoped examples. Not anchor 5 because there is no failure-recovery loop (Step 5 does not say what to do if validation fails) and validation only runs in one of three modes; the destructive-operation cap at 3 does not apply since the skill explicitly never stages, commits, or pushes and applies only behavior-preserving fixes.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so there are no buried or nested references to fault. The single file is well-sectioned with a clear header hierarchy and no content that clearly belongs in a separate file. It is anchor 4 rather than 5 because the ~170-line body is entirely inline — the four sub-agent role specs could plausibly live in reference files — and the under-50-line simple-skill exception does not apply.

4 / 5

Total

16

/

20

Passed

Description

62%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.

A concise, specific description with good natural trigger terms, but it omits any explicit "when to use" guidance and carries noticeable overlap risk with generic code-review/refactor skills. Adding a "Use when..." clause with distinguishing triggers would raise both completeness and distinctiveness.

Suggestions

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

Include the common synonyms users say ("refactor", "clean up", "audit") in the description to strengthen trigger coverage.

Differentiate from generic review skills by naming what is distinctive: behavior-preserving fixes only, applied to a scoped diff, with optional validation.

DimensionReasoningScore

Specificity

The description lists several specific, qualified actions — "Review a diff for clarity and safe simplifications" and "optionally apply low-risk fixes" — with clear scope conditions ("optionally", "low-risk"). It falls short of anchor 5 because coverage is not comprehensive (e.g., reuse/efficiency review dimensions are absent), but exceeds anchor 3's bare 1-2 action listing.

4 / 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 explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the "what" is concrete and specific.

3 / 5

Trigger Term Quality

Natural trigger terms are present — "diff", "review", "clarity", "simplifications", "fixes" — which map well to what users would say. A few common synonyms ("refactor", "clean up") are missing, matching anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description is somewhat specific (diff-scoped, safety-qualified) but overlaps significantly with general code-review and refactor skills — requests like "review my changes" or "simplify this code" would plausibly match several similar skills. This sits at anchor 3 rather than 4 because the overlap with closely related review/refactor skills is real, not minor.

3 / 5

Total

14

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/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.