database-migrations

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

Quality

86%

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

72%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 executable code and commands across five tools, but its multi-step destructive/batch workflows lack explicit validation feedback loops, and it is a monolithic single file with no progressive disclosure into reference files.

Suggestions

Add explicit validation/verification feedback loops to destructive and batch workflows (e.g., after a batched backfill, verify row counts and confirm no NULLs remain before proceeding; after a migration, run a verification query before declaring success).

Consolidate the redundant 'When to Activate' and 'When to Use This Skill' lists into a single section to reduce duplication.

Move the per-tool reference material (full Prisma/Django/Drizzle/golang-migrate sections) into separate reference files under references/ and keep SKILL.md as an overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly lean with terse GOOD/BAD blocks, a checklist, and an anti-patterns table, but the 'When to Activate' and 'When to Use This Skill' lists overlap and the expand-contract pattern is described twice, leaving minor tightening possible.	4 / 5
Actionability	Provides copy-paste-ready executable SQL (CONCURRENTLY indexes, batched DO$$ backfill), real CLI commands for all four ORMs, and real schema/migration code covering the common cases.	5 / 5
Workflow Clarity	A pre-apply safety checklist and expand-contract timeline give a rough sequence, but for destructive/batch database operations the rubric caps workflow_clarity at 3 when explicit validate->fix->retry feedback loops are absent, and no post-migration verification step is provided.	3 / 5
Progressive Disclosure	No bundle files exist and the 337-line body is a single monolithic file with no references to separate per-tool reference files; section headers provide structure but content that could be split (full Prisma/Django/Drizzle sections) is inlined with no file-level navigation.	3 / 5
	Total	15 / 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 well-targeted: it names concrete capabilities, six tools/databases, and an explicit 'Use when' trigger. It is clearly distinguishable from other skills with negligible conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (schema changes, data migrations, rollbacks, zero-downtime deployments) and enumerates six named tools/DBs, matching the comprehensive-coverage anchor rather than the 'minor gaps' anchor at 4.	5 / 5
Completeness	Explicitly answers both what (migration best practices across named stacks and operations) and when ('Use when planning or implementing database schema changes') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural keywords users would say (database migration, schema changes, rollbacks, zero-downtime) plus named tools (PostgreSQL, MySQL, Prisma, Drizzle, Django, TypeORM, golang-migrate) give comprehensive coverage of synonyms and product names.	5 / 5
Distinctiveness Conflict Risk	A clear niche (database migrations) with specific named DBs/ORMs and an explicit trigger yields minimal overlap with 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/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.