Content
28%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 generic boilerplate: it names plausible deliverables but provides no executable guidance, no migration workflow, and references playbooks that do not exist. A user following it would have no concrete direction for an actual zero-downtime migration.
Suggestions
Replace the abstract Instructions with a concrete expand-contract workflow (e.g., add nullable column -> backfill in batches -> switch reads/writes -> drop old column) with explicit validation gates between phases.
Add executable SQL examples for the core cases: batched backfills, lock-safe index creation per engine, and a tested rollback script template.
Fix the dangling 'implementation playbooks' pointer by creating actual reference files (e.g., references/postgres.md, references/mysql.md) or removing the mention, and cut the fluff Resources/Context sentences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and does not over-explain known concepts, but it contains vague filler that earns no tokens: 'Focus on production-ready SQL migrations with... enterprise-grade safety mechanisms' in Resources, a Context section that restates the Overview, and boilerplate instructions. Not 4 because these padded passages could be cut without losing information. | 3 / 5 |
Actionability | The Instructions section is pure abstraction ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes') with no SQL, commands, or concrete steps anywhere in the body, and 'suggest checking implementation playbooks' points to playbooks that do not exist in the bundle. This matches the 1 anchor: it describes rather than instructs. | 1 / 5 |
Workflow Clarity | The numbered Output Format implies a rough order of deliverables, but no actual migration workflow is sequenced and there are no validation or rollback-execution checkpoints — for a destructive/batch database skill the missing feedback loops cap this at 3, and the near-total absence of defined steps lands it at 2. | 2 / 5 |
Progressive Disclosure | The body has organized sections and no bulky inlined content, but its only pointer to deeper material ('implementation playbooks') is a dangling reference with no file, path, or link, and no bundle files exist. Some structure, but references are not clearly signaled — a 3, not 4. | 3 / 5 |
Total | 9 / 20 Passed |