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.
The skill body is organized into clear sections and keeps the overview short, but it offers no executable guidance or validation checkpoints for a risky migration workflow, and its single detailed reference is a broken path to a missing file.
Suggestions
Provide concrete, executable guidance (sample migration scripts, diff/transform commands, or specific tool invocations) instead of abstract bullets.
Add an explicit sequenced workflow with validation checkpoints (e.g. analyze -> migrate in phases -> run comparison tests -> validate -> rollback on failure).
Either create resources/implementation-playbook.md or remove/correct the reference so the signaled detail file actually exists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient with clear sections, but the opening paragraph repeats the frontmatter description verbatim and the use/don't-use bullets are generic filler that could be tightened. | 3 / 5 |
Actionability | Instructions are high-level hints ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no executable code, commands, or concrete migration patterns, and the only detailed reference points to a non-existent file. | 2 / 5 |
Workflow Clarity | Migration is a risky/destructive multi-step operation, yet the Instructions give only three vague bullets with no sequenced steps and no validation/rollback checkpoints; the Output Format lists deliverables, not a verifiable workflow. | 2 / 5 |
Progressive Disclosure | The body is well-sectioned and signals one detail reference ('resources/implementation-playbook.md'), but that referenced file does not exist in the bundle, breaking the navigation path it advertises. | 3 / 5 |
Total | 10 / 20 Passed |