database-migrations

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate). Use when writing a schema or data migration, planning a rollback, or aiming for zero-downtime deployment.

Quality

85%

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

78%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.

Highly actionable, executable content with strong sequencing and a pre-flight checklist, but it is a long monolithic file with no progressive disclosure to bundle references. Splitting per-tool details into reference files would lift the structure score.

Suggestions

Move per-ORM workflow and schema examples (Prisma, Drizzle, Kysely, Django, golang-migrate) into separate reference files under references/, keeping SKILL.md as an overview with one-level-deep links.

Add an explicit post-migration validation/rollback feedback loop (apply -> verify on copy of prod -> rollback plan if check fails) to satisfy the destructive/batch-operation feedback-loop expectation.

Trim explanatory asides such as the inline rationale comments to tighten token efficiency toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is dense and code-driven with little padding, but the per-ORM walkthroughs and a few explanatory asides could be trimmed slightly to reach the lean anchor.	4 / 5
Actionability	Copy-paste-ready SQL, CLI commands, and ORM code are provided throughout, covering the common cases (add column, concurrent index, backfill, expand-contract) concretely.	5 / 5
Workflow Clarity	The Migration Safety Checklist, phased expand-contract strategy, and day-by-day timeline give clear sequencing with checkpoints; however an explicit validate-then-rollback feedback loop for failed migrations is only implicit.	4 / 5
Progressive Disclosure	No bundle files exist and no references are signaled; the single file inlines full per-ORM sections that could be split out, though section structure itself is clear.	3 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong, third-person description that crisply states capabilities and explicit trigger conditions with named tooling. Minor keyword-synonym gaps keep trigger_term_quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("schema changes, data migrations, rollbacks, and zero-downtime deployments") across named tools and databases, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly states both what it does (migration best practices across named stacks) and when to use it ("Use when writing a schema or data migration, planning a rollback, or aiming for zero-downtime deployment").	5 / 5
Trigger Term Quality	Natural trigger phrases like "writing a schema or data migration, planning a rollback, zero-downtime deployment" give good coverage, though a few common synonyms (e.g. bare "migration", "alter table") are not surfaced.	4 / 5
Distinctiveness Conflict Risk	The database-migration niche is specific with named ORMs and concrete triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/database-migrations/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.