Content
65%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 body is dense with executable, copy-paste-near Drizzle code and avoids explaining concepts Claude already knows, making it a strong working reference. Its weaknesses are the missing scaffold workflow with validation checkpoints (notably no verify step around migrations/push), duplicated command listings, and the absence of any progressive disclosure — a long single file where reference material is inlined.
Suggestions
Add an explicit numbered scaffold workflow with a validation checkpoint, e.g. 1. install 2. write drizzle.config.ts 3. define schema 4. `npx drizzle-kit check` 5. `generate` → verify the SQL 6. `migrate` — the missing validate-before-migrate loop caps workflow clarity.
Move full repository implementations, the migration runner, and Integration Notes into references/ files (e.g. references/repositories.md) and keep a quick-start overview in SKILL.md.
De-duplicate the command lists (merge "Database Initialization" into "Common Commands") and drop the blockquote repeating the frontmatter description; also fix the missing `posts` import in findUserWithPosts and add the dev-dependency flags to the MySQL/SQLite install lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is code-heavy with lean, non-obvious prose ("generate creates SQL from schema diffs", "Use relational API for reads with joins, SQL-like API for inserts/updates/deletes") and assumes Claude's competence rather than explaining concepts. Not 5: there is redundancy — the frontmatter description is repeated verbatim as a blockquote, and "Database Initialization" duplicates four of the six commands re-listed under "Common Commands". | 4 / 5 |
Actionability | Nearly everything is executable: install commands per dialect, a complete drizzle.config.ts, connection setup, full schema/relations/repositories/transaction examples, and the full drizzle-kit command set. Not 5: minor gaps break copy-paste readiness — findUserWithPosts uses posts without importing it, and the install commands omit -D typescript/@types/node/tsx for the MySQL and SQLite variants. | 4 / 5 |
Workflow Clarity | The scaffold sequence is implied by section order (install → config → schema → push/generate/migrate → studio), but there is no explicit numbered workflow and no validation checkpoints — drizzle-kit check is listed as a bare command, never wired into a validate-before-migrate step. Per the scoring notes, database operations without feedback loops cap workflow_clarity at 3. Not 4: no verify/recover loop exists for the risky operations (push, migrate, drop). | 3 / 5 |
Progressive Disclosure | Sections are well-organized with clear headers, but the ~390-line file inlines full reference-grade material — complete repository implementations, the programmatic migration runner, and integration notes — that belongs in one-level-deep reference files. Not 2: structure is good, not minimal; not 4: no content is split out to separate files, so the overview-vs-detail split the anchor rewards is absent. | 3 / 5 |
Total | 14 / 20 Passed |