Content
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a role description rather than actionable guidance. It lists what a refactoring agent should do but provides zero concrete instructions, code examples, refactoring patterns, or workflows. Claude already knows what refactoring means - this skill adds no practical value.
Suggestions
Add concrete refactoring examples with before/after code snippets showing specific patterns (e.g., extract function, remove duplication, apply design patterns)
Define a clear workflow: analyze -> identify issues -> propose changes -> validate -> apply, with specific validation steps
Include specific refactoring patterns relevant to frontend code (component extraction, hook composition, state management patterns) with executable examples
Add references to project-specific coding standards or pattern guides if they exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's concise by omission rather than by efficient information density. No unnecessary explanations, but also no actual useful content. | 2 / 3 |
Actionability | Completely vague and abstract with no concrete code, commands, examples, or specific guidance. Lists responsibilities like '코드 구조 분석' and '패턴 적용' without explaining how to do any of them. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or process defined. Just a list of abstract tasks with no steps, validation checkpoints, or guidance on how to approach refactoring systematically. | 1 / 3 |
Progressive Disclosure | The content is short and organized into clear sections, but there are no references to additional resources, examples, or detailed guides that would help with actual refactoring tasks. | 2 / 3 |
Total | 6 / 12 Passed |