CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-simplify

Review a PR for code that can be deleted or simplified. Use when asked to review for simplicity or unnecessary edge-case overengineering.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally lean body that packs clear review criteria and an explicit decision preference into a handful of sentences, with an unambiguous single-action workflow appropriate to a simple skill. Its one real weakness is actionability: it never specifies how findings should be reported or applied, and offers no concrete example to calibrate what counts as overengineering.

Suggestions

Add one concrete example of a qualifying finding (e.g., a defensive fallback for an error condition that cannot occur) to calibrate what 'overengineering unlikely to affect customers' means in practice.

State what to do with findings — e.g., 'Report each finding with file:line references and the suggested deletion' — since the body never says whether to report or apply changes.

Sharpen the keep-vs-delete bar, e.g., 'Do not suggest deleting code that guards security, data loss, or recently reported issues' so the delete preference has an explicit boundary.

DimensionReasoningScore

Conciseness

The body is six short sentences with zero padding: "Review this PR.", "We prefer to delete code." — it assumes Claude's competence and never explains concepts Claude already knows. Every token earns its place; nothing could be cut without losing information.

5 / 5

Actionability

The guidance is concrete about evaluation criteria ("Is there anything that can be deleted or simplified given the end state of the branch?", "edge cases that resulted in overengineering which are unlikely to truly affect customers") but incomplete: no examples of qualifying findings, no output format, and no statement of whether to report findings or apply changes. It is not 2 because the criteria are specific and directive, not high-level hints; it is not 4 because key execution details are missing for an instruction-only skill.

3 / 5

Workflow Clarity

This is a simple, single-purpose, read-only review skill under 50 lines, and the single action is unambiguous: the body sequences it naturally — "Make sure you understand every product decision and change in functionality" first, then the two evaluation questions, then the decision rule "We prefer to delete code." No destructive or batch operation is performed, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is a single ~10-line body with no external files needed, and no references/scripts/assets directories exist in the bundle — consistent with the flat structure. It is trivially navigable with no monolithic content or buried references, matching the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

75%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 solid description that clearly and concisely states both what the skill does and when to use it, in third person, with reasonably natural trigger terms. Its main limitation is a narrow trigger enumeration and no synonym coverage, which slightly limits discoverability and keeps it a step below the exemplar descriptions.

DimensionReasoningScore

Specificity

Phrases like "Review a PR for code that can be deleted or simplified" and "unnecessary edge-case overengineering" name the domain (PR review) and several concrete actions (identify deletable code, simplify, flag overengineered edge cases). It is not 3, because more than 1-2 concrete actions are named; it is not 5, because coverage has minor gaps (nothing about how findings are surfaced or other review dimensions).

4 / 5

Completeness

Both parts are explicitly present: the "what" ("Review a PR for code that can be deleted or simplified") and the "when" ("Use when asked to review for simplicity or unnecessary edge-case overengineering"). It is not 3 because the when-clause is explicit rather than implied; it is not 5 because the trigger enumeration is narrow (only two trigger conditions, missing synonyms like "simplify" or "clean up").

4 / 5

Trigger Term Quality

"review for simplicity" and "unnecessary edge-case overengineering" are natural phrases a user would say when they need this skill. It is not 5 because common synonyms and variations are missing ("simplify", "clean up", "dead code", "delete unused code").

4 / 5

Distinctiveness Conflict Risk

The deletion/simplification niche with triggers like "simplicity" and "edge-case overengineering" is mostly distinct from general code-review skills. It is not 5 because "review a PR" overlaps broadly with any PR-review skill before the qualifier kicks in.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

every-app/open-seo

Path

.agents/skills/review-simplify/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.