db-migrate

Author or review a Drizzle DB migration for zero-downtime safety — expand/contract phasing, backward-compatibility with the deployed app version, and writing the `-- migration-safe` acknowledgment the check:migrations lint requires. Use when adding/editing files under `packages/db/migrations/` or changing `packages/db/schema.ts`.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clearly sequenced, validated workflow for destructive DB changes — a strong fit for the rubric's destructive-operation emphasis. Conciseness and progressive disclosure are slightly below the top anchor due to a justificatory rationale section and the absence of any reference-file split.

Suggestions

Tighten 'The window (why this matters)' to a sentence or two; the expand/contract section already conveys the discipline, so the rationale can assume Claude understands deploy cutover.

Consider extracting the per-operation playbook table into a references file (e.g. references/playbook.md) referenced from SKILL.md to improve progressive disclosure toward the one-level-deep anchor.

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes Claude's competence (no generic 'what a migration is' preamble), but the 'The window (why this matters)' section spends tokens justifying the discipline that could be tightened; efficient with minor over-explanation.	4 / 5
Actionability	Fully executable guidance throughout — concrete commands (`bunx drizzle-kit generate`, `bun run check:migrations`, `bun run db:migrate`), a per-operation playbook table with exact SQL (`CREATE INDEX CONCURRENTLY`, `ADD CONSTRAINT ... NOT VALID`), and copy-ready annotation snippets.	5 / 5
Workflow Clarity	A numbered workflow with explicit validation checkpoints (the `check:migrations` lint gate, hard-error vs annotate-tier branching, local db:migrate verify) and feedback loops for destructive/batch operations, satisfying the destructive-operations validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections with a focused overview, but no bundle files exist and all content (including the sizable per-operation playbook) is inlined in a ~90-line file rather than split into references; structure is good but not the one-level-deep reference split of the top anchor.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct, clearly stating both the capabilities and the natural trigger conditions in concise third-person voice. It is among the strongest reference examples in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Author or review a Drizzle DB migration', 'expand/contract phasing', 'backward-compatibility with the deployed app version', and 'writing the `-- migration-safe` acknowledgment' — covering the task comprehensively.	5 / 5
Completeness	Explicitly answers both what ('Author or review a Drizzle DB migration for zero-downtime safety...') and when ('Use when adding/editing files under...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases appear in 'Use when adding/editing files under `packages/db/migrations/` or changing `packages/db/schema.ts`', plus domain terms like 'Drizzle DB migration' and 'zero-downtime' that a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche around Drizzle DB migrations tied to specific repository paths and a named lint gate, with minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/db-migrate/SKILL.md
Commit: 417ae20

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.