Content
78%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, highly actionable reference with executable examples and genuinely non-obvious guidance (expand-contract, concurrent indexing, batched backfills) organized under clear headers. Its weaknesses are the absence of any progressive disclosure — everything is inlined in one large SKILL.md with no references/ files — and the lack of an explicit post-migration validation/feedback loop.
Suggestions
Split the per-ORM sections into one-level-deep reference files (e.g., references/prisma.md, references/django.md) and keep SKILL.md as the overview + PostgreSQL patterns + safety checklist.
Add an explicit post-apply validation loop: run the tool's status command (e.g., 'prisma migrate status', 'migrate ... up' exit code), verify schema, and fix/retry on failure — especially given destructive/batch operations.
Trim token cost by cutting the Timeline Example and per-ORM schema samples (Claude can generate idiomatic Prisma/Drizzle schemas already), keeping only tool-specific migration gotchas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Code-first and dense; comments carry only non-obvious facts ('Postgres 11+ is instant, no rewrite', 'CONCURRENTLY cannot run inside a transaction block') rather than re-explaining basics. Not 5: at ~430 lines, sections like the Timeline Example and per-ORM schema samples add tokens beyond what the core guidance needs. | 4 / 5 |
Actionability | Fully executable throughout: copy-paste-ready SQL with GOOD/BAD contrasts, complete CLI workflows per tool, full migration file examples (Kysely, golang-migrate, Django), and a batching DO-block that covers the common large-table case. | 5 / 5 |
Workflow Clarity | Clear sequencing with most checkpoints present: a pre-flight Migration Safety Checklist, expand-contract phases with 'Verify data consistency', code-first-then-drop-column ordering, and dirty-state recovery via 'migrate force VERSION'. Not 5: no explicit post-apply validation loop (e.g., verify migration status/schema, fix and retry on failure), which matters for destructive database operations. | 4 / 5 |
Progressive Disclosure | No bundle files exist and all ~430 lines are inline. Section headers are clear, but the per-ORM guides (Prisma, Drizzle, Kysely, Django, golang-migrate) each cover workflow + schema + advanced usage and clearly belong in separate one-level-deep reference files, matching the anchor for content that should be separate being inline. | 3 / 5 |
Total | 16 / 20 Passed |