refactor-html
Refactor HTML/TSX files to use existing UI components, DaisyUI classes, and semantic colors. Use when (1) refactoring React/TSX page components to use reusable UI components, (2) replacing raw HTML elements with component library equivalents, (3) converting primitive Tailwind colors to semantic DaisyUI colors, (4) extracting repeated styling patterns into components.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently communicates refactoring rules through concise tables and clear mappings. The main weakness is the workflow section, which lists steps but lacks validation checkpoints that would help catch refactoring errors before completion. Overall, it's actionable and token-efficient.
Suggestions
Add a validation step to the workflow (e.g., 'Run type-check to verify imports and props are correct' or 'Verify no TypeScript errors after refactoring')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference instead of verbose explanations. No unnecessary context about what HTML, TSX, or DaisyUI are—assumes Claude's competence. | 3 / 3 |
Actionability | Provides concrete before/after mappings with exact component names and class replacements. The tables serve as executable lookup references that Claude can directly apply. | 3 / 3 |
Workflow Clarity | Steps are listed but lack validation checkpoints. For refactoring operations, there's no verification step (e.g., 'run type-check' or 'verify component renders') before reporting completion. | 2 / 3 |
Progressive Disclosure | Appropriately structured with a clear overview and one-level-deep reference to components.md for detailed component props. Content is well-organized without being monolithic. | 3 / 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.
- Repository
- yahsan2/static-admin
- Commit
f734087
- 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.