Content
36%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 well-organized, brief shell whose actual instructional content is missing: generic placeholder instructions, no executable steps or validation checkpoints for a risky batch domain, and a resource pointer to a file that is absent from the bundle. The skill reads as an unfilled template rather than operational guidance.
Suggestions
Add the referenced `resources/implementation-playbook.md` (or correct its path) — the bundle contains no reference files, so the only detailed-guidance pointer is dangling.
Replace the abstract Instructions ("Apply relevant best practices") with concrete, executable steps: e.g. `npx react-codemod rename-unsafe-lifecycles`, upgrade sequences per React version, and migration patterns for class-to-hooks.
Define an ordered workflow with explicit validation checkpoints (run tests after each codemod, verify build after version bump) appropriate to batch codebase transformations.
Delete the verbatim description echo under the H1 and the tautological "Do not use" bullets to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and well-sectioned with no concept explanations Claude already knows, but it carries padding: the line under the H1 duplicates the frontmatter description verbatim, the "Do not use this skill when" bullets ("The task is unrelated to react modernization") are tautological, and the Instructions bullets are generic filler. Mostly efficient with some unnecessary content that could be trimmed — not 2 because no section teaches known concepts and total length is small. | 3 / 5 |
Actionability | The instructions are pure abstraction — "Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes" — with no commands, code, library names, or codemod invocations anywhere. The single concrete directive ("open `resources/implementation-playbook.md`") points to a file that does not exist in the bundle. Not 1 because the trigger scenarios and resource pointer constitute minimal concrete guidance; not 3 because there is no executable guidance at all. | 2 / 5 |
Workflow Clarity | Only a loose abstract order exists (clarify goals → apply best practices → validate outcomes); no sequenced concrete steps and no validation checkpoints for what is inherently a risky, batch-oriented process (version upgrades and automated codemod rewrites of entire codebases). Validation appears only as a nominal phrase, not a checkpoint. Not 1 because a rough logical sequence is present; not 3 because the steps are poorly defined and validation is absent as an actual gate. | 2 / 5 |
Progressive Disclosure | The body has clean, clearly labeled sections and a well-signaled one-level-deep reference (mentioned in both Instructions and Resources), but `resources/implementation-playbook.md` does not exist anywhere in the bundle — the disclosure chain is broken, so the promised detail layer cannot be reached. Not 4/5 because the referenced detail file is missing; not 2 because in-body structure is good and the reference is clearly signaled rather than buried. | 3 / 5 |
Total | 10 / 20 Passed |