Content
81%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-structured, actionable body that concentrates on non-obvious Drizzle migration pitfalls and embeds explicit validation and feedback loops for destructive operations. The main slack is minor verbosity in the worked-example commentary and a few placeholder-driven gaps in the diagnostic script.
Suggestions
Tighten the "What it demonstrates" bullets under the worked example — the explicit-column-naming and singular-snake_case points are already visible in the code; keep only the non-obvious constraint note.
In the out-of-sync diagnostic bash script, show how to resolve <out> and <table> from drizzle.config.ts (or note they come from the layout detection) so the snippet is copy-paste ready.
Consider moving the extended "If the history is already out of sync" repair procedure into a references/ file, leaving SKILL.md with the symptom + pointer, to reduce body length while preserving the detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and skill-specific (journal desync, rename-as-drop data loss, money-column convention detection are non-obvious knowledge worth keeping), but the "What it demonstrates" bullets restate points already visible in the worked example and could be trimmed. | 4 / 5 |
Actionability | Provides executable code (pgTable definitions with explicit column naming, FK example), concrete commands (npx drizzle-kit generate, git status --short), and a runnable diagnostic script; minor gaps are the <out>/<table> placeholders and the schema-edit step being left implicit. | 4 / 5 |
Workflow Clarity | An explicit 8-step workflow with validation checkpoints (read emitted SQL before committing, verify entity/relationship/constraint coverage) and a clear feedback loop — if an unintended DROP appears, fix the schema and regenerate — satisfying the destructive-operation feedback-loop requirement. | 5 / 5 |
Progressive Disclosure | Well-organized into clearly labeled sections with one-level-deep, clearly signaled external references (project-layout.md, mcp-servers.md); no bundle files exist to verify, and a few sections (money columns, out-of-sync repair) could arguably live in references but are appropriately core here. | 4 / 5 |
Total | 17 / 20 Passed |