Conciseness

Every bullet is a dense, non-obvious fact ('omit { schema } and the db.query.* relational API silently does not exist'; 'A column rename generates DROP + ADD'), with zero padding and no explanation of concepts Claude already knows.

Actionability

Concrete API recipes appear throughout (sql.placeholder('id') + .prepare('name') then .execute({ id }); postgres(url, { max: 1 }) followed by migrate(drizzle(client), { migrationsFolder: './drizzle' }); a copy-paste ALTER TABLE RENAME COLUMN statement), but they are inline fragments rather than complete executable examples covering the common cases.

Workflow Clarity

Migration workflows are clearly sequenced ('generate → review the SQL in the out dir → migrate'; the two-migration pattern for non-nullable columns) with validation checkpoints present (reviewing generated SQL, the check command), so the destructive-operation cap does not apply — but there are no explicit error-recovery loops.

Progressive Disclosure

The body is under 50 lines with two well-organized sections (Gotchas, drizzle-kit) and needs no external reference files, satisfying the simple-skill exception for full marks.

Specificity

The description lists multiple concrete capabilities — 'schemas, type-safe and relational queries, transactions and drizzle-kit migrations for PostgreSQL, MySQL and SQLite' — giving comprehensive coverage of the tool's surface with no meaningful gaps.

Completeness

It explicitly answers both what it does (the opening capability list) and when to use it ('Use when defining a Drizzle schema, writing Drizzle queries, or running drizzle-kit') with concrete trigger phrases.

Trigger Term Quality

Natural trigger phrases like 'defining a Drizzle schema, writing Drizzle queries, or running drizzle-kit' are present and well-chosen, but common variations users might say (e.g. 'ORM', 'migrate', 'drizzle.config') are missing.

Distinctiveness Conflict Risk

Every trigger is gated on the distinctive 'Drizzle' name ('Drizzle schema', 'Drizzle queries', 'drizzle-kit'), creating a clear niche with minimal conflict risk against generic SQL or dialect-specific skills.