Content
40%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.
The body is well-structured and lean but nearly empty of actionable guidance: instructions are generic best-practice platitudes, there is no executable workflow or validation for risky batch migrations, and the single referenced resource file does not exist in the bundle. The skill relies entirely on a playbook that is absent.
Suggestions
Ship the referenced file (or fix the path): create 'resources/implementation-playbook.md' with the detailed patterns and examples the body promises, since the entire skill currently depends on it.
Replace the vague instruction bullets with concrete, executable steps — e.g., codemod commands ('npx react-codemod rename-unsafe-lifecycles'), version-specific breaking-changes checks, and a class-to-hooks migration pattern example.
Define a validation loop for the upgrade workflow (run test suite / typecheck after each migration step, fix, and re-run) since React upgrades are batch operations across a codebase, and cut the tautological 'Do not use' bullets that add no information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no React-concept padding, but the two tautological 'Do not use' bullets ('The task is unrelated to react modernization', 'You need a different domain or tool outside this scope') and the generic instruction bullets are trimmable filler. | 4 / 5 |
Actionability | The instructions are high-level hints — 'Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes' — with no code, commands, or specific steps (no codemod invocations, no migration steps, no breaking-changes guidance), and the only concrete pointer ('open resources/implementation-playbook.md') targets a file that does not exist in the bundle. | 2 / 5 |
Workflow Clarity | A rough implied sequence exists (clarify → apply best practices → validate outcomes) but the steps are poorly defined and validation is only mentioned, never specified — a significant gap for batch/risky upgrade operations. | 2 / 5 |
Progressive Disclosure | Sections are present and the body correctly keeps detail out of SKILL.md, but the sole reference 'resources/implementation-playbook.md' is missing from the bundle entirely, so the navigation path leads nowhere and no detailed content is actually available. | 2 / 5 |
Total | 10 / 20 Passed |