code-simplicity-reviewer

Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/code-simplicity-reviewer/SKILL.md

Quality

Content

67%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 content is a well-structured, actionable instruction skill with a clear review process and concrete output template. Its main weakness is token padding in the preachy closing remark and examples block that assume knowledge Claude already has.

Suggestions

Trim the closing motivational paragraph ('Remember: Perfect is the enemy of good...') — Claude already understands these principles and they consume context without adding actionable guidance.

Consider shortening the <examples> block to one representative example, or move it to a references file, to reduce inline padding.

Tighten verbose bullets like 'Question the necessity of each line of code. If it doesn't directly contribute...' to denser imperatives that assume Claude's competence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with structured guidance, but the closing motivational paragraph ('Perfect is the enemy of good... Every line of code is a liability') and the examples block restate principles Claude already knows and could be trimmed.	3 / 5
Actionability	Concrete, actionable guidance throughout: six specific review categories with sub-bullets, a 5-step process, and a fill-in markdown output template that tells Claude exactly what to produce.	4 / 5
Workflow Clarity	A clear 5-step review sequence is present and the output template acts as a structural checkpoint; no destructive/batch validation cap applies since the skill only produces recommendations.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers, numbered lists, and a fenced output template; no bundle files exist and none are needed, though at ~95 lines the examples block is content that is inlined rather than split out.	4 / 5
	Total	15 / 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.

The description clearly conveys purpose and timing with a distinct YAGNI/simplicity niche, but its actions are somewhat generic and it lacks concrete user-utterance trigger phrases. Adding natural trigger terms and a sharper action list would lift it toward the top anchors.

Suggestions

Add concrete user-trigger phrases, e.g. 'Use when the user asks to simplify code, reduce complexity, or check for YAGNI violations after implementing a feature.'

Expand the action list with more specific behaviors (e.g. 'flag dead code, inline single-use helpers, collapse redundant conditionals') to improve specificity.

Include common synonyms users actually say ('refactor', 'clean up', 'over-engineered') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the code-simplicity domain and 1-2 concrete actions ('identify YAGNI violations and simplification opportunities'), but the actions are generic review verbs rather than a comprehensive specific list.	3 / 5
Completeness	Clearly answers what (final review pass to ensure simplicity, identify YAGNI violations) and when ('Use after implementation is complete'), but the when is a lifecycle timing rather than concrete user-utterance trigger phrases.	4 / 5
Trigger Term Quality	Includes some relevant natural terms ('simple', 'minimal', 'YAGNI', 'simplification') but misses common variations a user might say like 'refactor', 'clean up', or 'reduce complexity'.	3 / 5
Distinctiveness Conflict Risk	The YAGNI/simplicity-review framing carves a mostly distinct niche, with only minor overlap risk against general code-review skills.	4 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/code-simplicity-reviewer/SKILL.md
Commit: cce36d3

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.