Conciseness

The body is lean throughout: no explanation of what Drizzle or migrations are, every sentence carries a repo-specific rule or command ('never copy-paste a snapshot file without refreshing both IDs'). Each token earns its place against the 'assumes Claude's competence' anchor.

Actionability

Guidance is copy-paste ready across the board: 'pnpm db:generate', 'pnpm exec drizzle-kit generate --custom --name <name>', 'pg_dump --schema-only', 'pnpm docker:reset', plus concrete decision lists for choosing migration type and concrete drift signals. The common cases (generate, custom SQL, baseline reset) are each covered by specific commands.

Workflow Clarity

The default workflow has a review checkpoint (step 3, 'Review generated SQL and snapshot metadata together') and the drift rule ('stop and assume drift until proven otherwise') provides an error-recovery loop, and the destructive baseline-reset includes 'Review against the schema dump'. However, validation is described as 'review' rather than explicit executable checks (e.g., no command to verify the clean-tree no-op invariant), leaving minor gaps versus the fully-explicit-validation anchor.

Progressive Disclosure

The skill has no bundle files, and at ~90 lines of dense rules it is appropriately organized into well-labeled sections (trigger, workflow, migration type, round-trip rule, invariants, triage, baseline reset) with no content that clearly demands a separate file. It is above the under-50-line threshold where inline-only structure scores 5, and the baseline-reset procedure could arguably live in a reference file, so it sits at 'good structure, minor organization gaps' rather than the clear-overview-with-signaled-references anchor.

Specificity

The description names several concrete, specific triggers with exact paths and tool names — 'changing libs/database/src/schema.ts, adding Drizzle migrations, debugging drizzle-kit drift, or deciding between auto-generated and custom SQL migrations' — but it never states what the skill itself does, so coverage is several specific items with a gap rather than comprehensive.

Completeness

The 'when' is explicit and rich ('Use when changing... adding... debugging... deciding...'), but the 'what' is only weakly present — 'Includes the post-#867 baseline-reset rule' hints at content without saying what the skill provides. This sits between anchor 2 ('only when' present) and a full what+when pair, matching neither anchor cleanly.

Trigger Term Quality

Natural terms a user on this repo would say are well covered: 'schema.ts', 'Drizzle migrations', 'drizzle-kit drift', 'custom SQL migrations'. A few plausible variations are missing (e.g., 'db:generate', 'snapshot', 'pnpm db:*' commands), keeping it just short of the comprehensive-with-synonyms anchor 5.

Distinctiveness Conflict Risk

The niche is unambiguous: Drizzle migrations for this specific codebase, anchored by an exact file path, tool name, and an issue reference (#867). It would not plausibly trigger any other skill, matching the clear-niche anchor.