Content
72%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 highly actionable, Drizzle-specific reference with excellent executable code and current tooling syntax. Its weaknesses are structural: no validation/feedback loop in the migration workflow despite database operations, and a monolithic single-file layout with no progressive disclosure into reference files, plus rule repetition across three formats.
Suggestions
Add validation checkpoints to the migration workflow: review the generated SQL in the ./drizzle output before running 'drizzle-kit migrate', apply migrations to a staging copy first, and state how to recover when a migration fails partway (the rubric caps database/batch workflows without feedback loops at workflow_clarity 3).
Split dialect-specific material (the PostgreSQL schema and connection variants, and the detailed upsert patterns) into a references/ file (e.g., references/dialects.md) linked one level deep, so SKILL.md serves as an overview rather than a monolithic ~430-line file.
Trim the triple repetition of each rule (inline code comment + 'Key rules' bullet + final Checklist): keep the checklist as the single consolidated rule list and compress the per-section bullets to only the rules not already shown in code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and mostly code with Drizzle-specific non-obvious rules ('Drizzle does NOT auto-index foreign keys', 'SQLite has foreign keys OFF by default'), assuming Claude's competence rather than explaining basics. It is not 5 because key rules are stated three times each (inline code comments, 'Key rules' bullet lists, and the final Checklist), and the schema section repeats near-identical table definitions for the SQLite and PostgreSQL variants. | 4 / 5 |
Actionability | Every section contains complete, copy-paste-ready TypeScript and shell commands: full schema definitions, current drizzle-kit commands ('npx drizzle-kit generate' / 'migrate' / 'push'), atomic upsert code, transaction patterns, and connection setup with pragmas. This matches the anchor for fully executable guidance covering the common cases; not 4 because there are no significant gaps in the code shown. | 5 / 5 |
Workflow Clarity | The migration sequence is listed (define schema, configure dialect, generate, migrate, commit files) and 'push' is correctly gated to prototyping, but there are no validation checkpoints: no instruction to review the generated SQL before applying, verify migration success, or recover from a failed migration. Per the rubric, database operations lacking feedback loops cap this at 3; it is not 2 because the sequence itself is coherent and well-ordered. | 3 / 5 |
Progressive Disclosure | The body has clear section headers, a summary checklist, and verifier links, so structure is present. However, the entire ~430-line reference (including dialect-specific schema/connection variants and detailed upsert patterns) is inlined in one file with no in-bundle reference files at all (no references/, scripts/, or assets/ exist), so content that could be split out is inline and navigation is single-file only. Not 4 because a file this size with zero one-level-deep reference split exceeds 'minor organization gaps'. | 3 / 5 |
Total | 15 / 20 Passed |