frontend-refactor
코드 리팩토링 에이전트. 코드 구조를 개선하고 리팩토링합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill frontend-refactor35
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
14%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 skill description is too vague and generic to effectively guide skill selection. It lacks specific actions, explicit trigger conditions, and distinctive characteristics that would help Claude choose it over other code-related skills. The description needs substantial improvement across all dimensions.
Suggestions
Add specific refactoring actions such as 'extract methods, rename variables, reduce cyclomatic complexity, eliminate code duplication, apply design patterns'
Include an explicit 'Use when...' clause with trigger terms like 'refactor', 'clean up code', 'improve code quality', 'reduce complexity', 'code smell'
Add distinctive triggers that separate this from general coding skills, such as 'when user wants to restructure existing code without changing functionality'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like '코드 구조를 개선하고 리팩토링합니다' (improves code structure and refactors) without listing specific concrete actions such as extracting methods, renaming variables, reducing complexity, or removing duplication. | 1 / 3 |
Completeness | The description only weakly addresses 'what' (improves code structure) and completely lacks a 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like '리팩토링' (refactoring) and '코드' (code), but misses common variations users might say such as 'clean up code', 'improve readability', 'reduce duplication', 'extract method', or 'code smell'. | 2 / 3 |
Distinctiveness Conflict Risk | Very generic description that could easily conflict with any code-related skill - code review, code generation, debugging, or general coding assistance skills would all potentially overlap. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
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 |
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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.