Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong workflow-oriented skill body: fully executable commands with real paths, a clearly sequenced six-step process with dry-run validation and error-recovery loops, and clean progressive disclosure into verified per-source reference files. Its only weakness is prose density — a handful of sentences pack multiple clauses and would benefit from being split or trimmed.
Suggestions
Split the most clause-heavy sentences (the Font Awesome/Icon rules in the bulma-classes headline, the step-1 HTML-module paragraph) into shorter declarative statements or a small list — the information density is high but several sentences require multiple reads to parse.
Move or compress the version-history asides inside the source table (e.g. "abandoned 2019, pins Bulma 0.7.5 plus four extensions") into the per-source reference pages, keeping only the decision-relevant fact (Bulma version gap) inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence throughout — no explanations of what React, Bulma, or codemods are — and nearly every token carries codemod-specific knowledge Claude cannot know (exit-code semantics, re-run safety, per-source risks), so token efficiency is high. It falls at 4 rather than 5 because several sentences are syntactically overloaded and could be tightened without losing information, e.g. "Font Awesome's own hidden `<i>` in a `.icon` that carries nothing else assistive tech reads becomes `Icon`, which hides the `.icon` instead, the glyph hidden either way" and the long paragraph in step 1 about HTML page modules. | 4 / 5 |
Actionability | Commands are copy-paste ready with real paths and flags: `pnpm dlx bestax-migrate <source> src/ --dry`, `pnpm dlx bestax-migrate bulma-classes src/pages/login/index.html --dry`, `pnpm dlx bestax-migrate bulma-classes -e html src/pages/ --dry`, `grep -rn "TODO(bestax-migrate)" src/`, `npm install`. The `<source>` placeholder is concretely resolved by the table, flags (--css bulma|keep, --no-deps, -e html,htm) are documented, and report entry types are named. This matches the 5 anchor's executable guidance covering the common cases; it is not 4 because there are no meaningful gaps in executable detail. | 5 / 5 |
Workflow Clarity | Six clearly ordered steps (dry-run → apply → install → resolve TODOs → stylesheet → finish) with explicit validation up front ("Dry-run the codemod... and review the report") and error-recovery feedback loops: "A file that fails to parse or transform... Fix that file and run the codemod on it again", plus re-run guidance after fixing a TODO and a final typecheck/build with side-by-side UI review. The batch-operation cap of 3 does not apply because validation checkpoints are explicit; this matches the 5 anchor (clear sequence, explicit validation, feedback loops). | 5 / 5 |
Progressive Disclosure | The body is an overview that drives the workflow while per-source detail is split one level deep into references/<source>/component-map.md, prop-map.md, unmappables.md plus the shared references/css-migration.md — all verified to exist and to contain the claimed content (e.g. dynamic-class and html-* recipes in references/bulma-classes/unmappables.md). References are clearly signaled via the source table and inline links, and the "Source-specific headlines" stay at headline level to inform source selection rather than duplicating the reference detail. This matches the 5 anchor: clear overview, well-signaled one-level-deep references, easy navigation. | 5 / 5 |
Total | 19 / 20 Passed |