simplify

Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.

1.68x

Quality

58%

Does it follow best practices?

Impact

91%

1.68x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/simplify/SKILL.md

Quality

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description has good structure with explicit 'what' and 'when' clauses, earning full marks for completeness. However, it lacks specific concrete actions (what exactly does 'simplify' mean?) and misses common trigger terms users would naturally use like 'clean up my code' or 'refactor'. The description could conflict with other code quality or refactoring skills.

Suggestions

Add specific concrete actions like 'rename variables for clarity, extract repeated logic into functions, simplify conditionals, improve formatting'

Include natural trigger terms users would say: 'clean up', 'refactor', 'polish', 'tidy up', 'make more readable'

Add distinguishing context to reduce conflict risk, such as specifying the types of simplification or the scope (e.g., 'cosmetic improvements only' vs 'structural refactoring')

Dimension	Reasoning	Score
Specificity	Names the domain (code) and some actions ('simplify', 'refine', 'improve readability'), but lacks specific concrete actions like 'rename variables', 'extract functions', 'remove duplication', or 'add comments'.	2 / 3
Completeness	Clearly answers both what ('Simplify and refine recently modified code for clarity and consistency') and when ('Use after writing code to improve readability without changing functionality') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms ('code', 'clarity', 'readability') but misses common variations users would say like 'clean up', 'refactor', 'polish', 'tidy', or 'code review'.	2 / 3
Distinctiveness Conflict Risk	Could overlap with general code review skills, refactoring skills, or linting skills. The phrase 'recently modified code' adds some distinction, but 'clarity and consistency' is fairly generic in the code quality space.	2 / 3
	Total	9 / 12 Passed

Implementation

50%

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

This skill provides a reasonable conceptual framework for code simplification but lacks the concrete, actionable guidance that would make it highly effective. It describes principles well but doesn't show them in action through before/after code examples. The workflow is present but lacks specific validation criteria.

Suggestions

Add 2-3 concrete before/after code examples demonstrating the simplification principles (e.g., nested ternary → switch statement, redundant abstraction removal)

Remove personality/expertise framing ('Your expertise lies in...', 'years as an expert') - Claude doesn't need this context

Add specific validation criteria for the refinement process (e.g., 'Run tests to verify functionality unchanged', 'Check that cyclomatic complexity decreased')

Link to or create an EXAMPLES.md with detailed refactoring patterns specific to the project

Dimension	Reasoning	Score
Conciseness	The content includes some unnecessary verbosity like 'Your expertise lies in...' and 'This is a balance that you have mastered as a result your years as an expert software engineer' which adds no actionable value. The principles are mostly relevant but could be tightened.	2 / 3
Actionability	Provides guidelines and principles but lacks concrete code examples showing before/after refactoring. The guidance is descriptive rather than demonstrative - no executable examples of what 'good' simplification looks like.	2 / 3
Workflow Clarity	Lists a 6-step refinement process but steps are vague ('Analyze for opportunities', 'Verify the refined code'). No validation checkpoints or concrete criteria for when simplification is complete or correct.	2 / 3
Progressive Disclosure	Content is reasonably organized with numbered sections, but everything is inline. References CLAUDE.md for standards but doesn't link to examples or detailed guidance. Could benefit from linking to concrete examples file.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: brianlovin/claude-config
Commit: 1a9819e

Reviewed: 10 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.