code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, well-validated workflow and concrete examples, but it is somewhat verbose and ships as a single large file that would benefit from offloading detail into reference files.

Suggestions

Trim conceptual restatement Claude already knows — e.g. condense the Chesterton's Fence explanation and 'explicit beats compact' framing — to tighten conciseness.

Extract language-specific guidance (TypeScript/JavaScript, Python, React/JSX) into reference files under references/ and link to them one level deep, leaving the core principles and process in SKILL.md.

Move the extended pattern/signal/simplification tables and the Common Rationalizations table into a separate reference to reduce inline length while keeping navigation explicit.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly earns its tokens via tables, before/after code, and checklists, but it restates concepts Claude already knows (e.g. the extended Chesterton's Fence explanation and 'explicit code is better than compact code' truisms) and could be tightened.	2 / 3
Actionability	Provides fully concrete, executable guidance — pattern/signal/simplification tables, runnable TypeScript/Python/React before/after examples, the Rule of 500, and a copy-ready incremental process.	3 / 3
Workflow Clarity	The four-step process (Understand → Identify → Apply → Verify) has explicit validation checkpoints — 'Run tests after each change', 'If tests fail → revert and reconsider' — plus a final verification checklist, with feedback loops appropriate to batch/behavior-sensitive refactoring.	3 / 3
Progressive Disclosure	The skill is a single ~325-line monolithic file with no bundle references; language-specific guidance and extended tables that could live in reference files are inline. Sections are well organized, but at this length content is not appropriately split into one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 is strong: it states concrete capabilities, supplies explicit natural-language triggers, covers both what and when, and occupies a distinct behavior-preserving-simplification niche. Voice is correctly third person.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Simplifies code for clarity', 'refactoring code for clarity without changing behavior', and 'reviewing code that has accumulated unnecessary complexity' — matching the top anchor rather than the single-domain mid anchor.	3 / 3
Completeness	Explicitly answers what it does ('Simplifies code for clarity... without changing behavior') and when to use it via three explicit 'Use when...' trigger clauses.	3 / 3
Trigger Term Quality	Three 'Use when' clauses cover natural phrases a user would say — 'refactoring code for clarity', 'harder to read, maintain, or extend', and 'unnecessary complexity' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The behavior-preserving clarity niche with triggers like 'harder to read, maintain, or extend' and 'accumulated unnecessary complexity' carves a clear niche unlikely to conflict with unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: addyosmani/agent-skills
Commit: 70b7506

Reviewed: 3 days 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.