code-refactoring-assistant
Executes refactorings — extract method, inline, rename, move — in small, behavior-preserving steps with a test between each. Use when the user wants to restructure working code, when cleaning up after a feature lands, or when a smell has been identified and needs fixing.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill code-refactoring-assistant97
Quality
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
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.
This is an excellent skill description that clearly articulates specific refactoring operations, uses natural developer terminology, and provides explicit 'Use when' guidance with multiple trigger scenarios. The description is concise yet comprehensive, using third person voice appropriately and distinguishing itself clearly from general coding skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'extract method, inline, rename, move' and describes the methodology 'small, behavior-preserving steps with a test between each'. | 3 / 3 |
Completeness | Clearly answers both what ('Executes refactorings — extract method, inline, rename, move — in small, behavior-preserving steps with a test between each') and when ('Use when the user wants to restructure working code, when cleaning up after a feature lands, or when a smell has been identified'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'refactorings', 'extract method', 'inline', 'rename', 'move', 'restructure', 'cleaning up', 'smell'. These are standard developer vocabulary for refactoring tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on refactoring operations with distinct triggers like 'extract method', 'inline', 'rename', 'move', 'smell', and 'behavior-preserving'. Unlikely to conflict with general coding or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently teaches refactoring mechanics through well-structured tables, a clear workflow rhythm, and a concrete worked example. The content respects Claude's intelligence while providing actionable, executable guidance. Minor improvement possible in how external skill references are organized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place—tables compress mechanics efficiently, the rhythm diagram is minimal yet clear, and there's no explanation of what refactoring is beyond the one-line definition. Assumes Claude knows programming concepts. | 3 / 3 |
Actionability | Provides fully executable Python code in the worked example, specific mechanics for each refactoring type in table form, and a concrete step-by-step process. The output format template is copy-paste ready. | 3 / 3 |
Workflow Clarity | The rhythm section explicitly shows the test→step→test→commit loop with a clear revert path on red. The worked example demonstrates validation at each step (Steps 3 and 5), and every commit is described as a safe revert point. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but references to external skills (code-smell-detector, behavior-preservation-checker) are mentioned inline without clear navigation structure. The skill is appropriately self-contained but could better signal these as optional deep-dives. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%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.
- 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.