code-refactoring-refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
32
26%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/code-refactoring-refactor-clean/SKILL.mdQuality
Discovery
32%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 identifies a clear domain (code refactoring) and references relevant methodologies (SOLID, clean code), but it reads more like a system prompt persona definition than a skill description. It lacks explicit trigger guidance ('Use when...'), uses second-person framing implicitly via imperative voice ('Analyze and refactor the provided code'), and lists abstract outcomes rather than concrete actions.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to refactor code, reduce technical debt, fix code smells, apply SOLID principles, or improve code structure.'
Replace abstract outcomes ('improve quality, maintainability, and performance') with concrete actions like 'extract methods, decompose large classes, rename for clarity, remove duplication, simplify conditional logic.'
Rewrite in third-person descriptive voice (e.g., 'Analyzes and refactors code to apply clean code principles...') instead of the current imperative/persona style ('You are a code refactoring expert...').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (code refactoring) and some actions ('analyze and refactor'), but the specific capabilities are vague — 'improve quality, maintainability, and performance' are abstract outcomes rather than concrete actions like 'extract methods, rename variables, decompose classes'. | 2 / 3 |
Completeness | Describes what it does (analyze and refactor code) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'refactoring', 'clean code', 'SOLID', and 'design patterns', but misses common user variations like 'code smell', 'technical debt', 'simplify code', 'restructure', or 'DRY'. The terms lean more toward textbook jargon than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'refactoring', 'SOLID', and 'clean code principles' provides some distinctiveness, but the broad scope of 'improve quality, maintainability, and performance' could easily overlap with general code review, linting, or performance optimization skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic, high-level description of code refactoring that provides no concrete, executable guidance—no code examples, no specific patterns, no real commands. It reads more like a role prompt than an actionable skill. The referenced playbook file does not exist in the bundle, undermining the progressive disclosure strategy.
Suggestions
Add concrete, executable code examples showing before/after refactoring for at least 2-3 common patterns (e.g., Extract Method, Replace Conditional with Polymorphism).
Replace vague instructions like 'Assess code smells' with specific steps: e.g., 'Run complexity analysis, identify methods >20 lines, flag functions with >3 parameters'.
Include the `resources/implementation-playbook.md` bundle file with detailed patterns, or inline the most critical patterns directly in the skill.
Remove boilerplate sections (Context restating the description, generic Limitations) to improve token efficiency and focus on actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains things Claude already knows—what code smells are, when to use refactoring, generic 'context' sections restating the description, and boilerplate limitations. The 'Use this skill when' / 'Do not use this skill when' sections add little value. The '$ARGUMENTS' placeholder is unexplained filler. | 1 / 3 |
Actionability | The instructions are entirely abstract ('Assess code smells', 'Propose a refactor plan', 'Apply changes in small slices') with zero concrete code examples, specific commands, patterns, or executable guidance. There is nothing copy-paste ready or specific enough to differentiate this from generic advice. | 1 / 3 |
Workflow Clarity | There is a rough sequence (assess → plan → apply → test), but no explicit validation checkpoints, no feedback loops for error recovery, and no concrete verification steps. The instruction to 'Update tests and verify regressions' is vague rather than actionable. | 2 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files are provided, so the reference is unverifiable and potentially broken. The main file itself is somewhat structured but includes sections that could be trimmed rather than split. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
79d9c42
- 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.