CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify-code

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

58

Quality

68%

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-claude/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.

The body is a well-structured, concise, actionable workflow with explicit validation and clear sequencing across its six steps. All dimensions land at a strong 4, with only minor gaps preventing maximal scores.

DimensionReasoningScore

Conciseness

The body is lean and instruction-focused with no concept re-explanation, but has minor trim opportunities such as the repeated "Recommended sub-agent role" lines and "When to Use" content that overlaps the description, fitting anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Provides concrete git diff commands, a specific finding shape, named modes, and concrete fix types; minor gap is the absence of literal copy-paste sub-agent prompt templates, fitting anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit validation step (Step 5) and a discard-weak-findings checkpoint; the destructive/batch cap does not apply because validation is present, but the validate->fix->retry loop is not spelled out as iterative and validation is mode-gated, fitting anchor 4.

4 / 5

Progressive Disclosure

A single self-contained file with clear section headers and well-organized content; no bundle files exist and nothing obviously needs splitting out, fitting anchor 4 rather than anchor 5 which requires clearly signaled one-level-deep references.

4 / 5

Total

16

/

20

Passed

Description

61%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 purpose and uses natural trigger terms but omits an explicit "Use when..." clause, leaving the trigger context implicit and capping completeness. It is concise and largely distinct from unrelated skills.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when the user asks to simplify, clean up, refactor, or review changed code."

Broaden the action list in the description to cover the skill's full scope (e.g., reuse, efficiency, clarity) so specificity moves from 1-2 actions toward comprehensive coverage.

Include common synonyms ("clean up", "refactor") directly in the description so trigger-term coverage reaches the comprehensive level.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Review a diff for clarity and safe simplifications", "optionally apply low-risk fixes") but the action list is not comprehensive, matching anchor 3 rather than the multi-action anchor 4.

3 / 5

Completeness

The "what" is clear but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains natural user terms ("Review", "diff", "simplifications", "fixes") with good coverage; misses some common synonyms like "clean up" and "refactor" that appear only in the body, fitting anchor 4 rather than the fully comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The diff-simplification / behavior-preserving-fix niche is mostly distinct but has minor overlap risk with closely related code-review and refactor skills, fitting anchor 4.

4 / 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.

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