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

88%

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

77%

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

A dense, highly actionable reference with executable patterns, clear checklists, and a well-sequenced expand-contract workflow. Its main weaknesses are redundancy between the two 'When to' sections and the anti-patterns table, and a monolithic structure that would benefit from splitting per-tool details into reference files.

Suggestions

Collapse the duplicate 'When to Activate' and 'When to Use This Skill' sections into one trigger list to remove redundancy.

Move the per-ORM sections (Prisma, Drizzle, Django, golang-migrate) into separate reference files (e.g. references/prisma.md) and link to them from a brief overview, reducing the monolithic SKILL.md body.

Trim the Anti-Patterns table where it restates the inline BAD/GOOD code comments, or keep the table and shorten the inline prose.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining basic concepts Claude knows and leads with executable patterns, but it is long and redundant: the 'When to Activate' and 'When to Use This Skill' sections overlap heavily, and the Anti-Patterns table rehashes the inline BAD/GOOD comments; not 1 because there is no concept padding, not 3 because the duplication could be tightened.	2 / 3
Actionability	Provides copy-paste-ready SQL, bash, Python, TypeScript, and Prisma schema examples with concrete GOOD/BAD comparisons; not 2 because the code is executable and complete rather than pseudocode.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced (expand-contract Phase 1/2/3 with a 'Verify data consistency' checkpoint) and the Migration Safety Checklist provides validation checkpoints for destructive/batch DB operations; not 2 because validation steps are present, satisfying the destructive-operations cap exception.	3 / 3
Progressive Disclosure	Sections are well-organized, but the ~340-line body is monolithic with no references — per-ORM guides (Prisma, Drizzle, Django, golang-migrate) are content that could be split into separate files; not 1 because organization is clear, not 3 because nothing is split and the file exceeds the 'simple skill' threshold for inline-only scoring.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 description that names concrete capabilities, specific tools, and an explicit 'Use when' trigger in third-person voice. It is concise without fluff and clearly scoped.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'schema changes, data migrations, rollbacks, and zero-downtime deployments' — alongside specific tools, matching the 'lists multiple specific concrete actions' anchor rather than the score-2 partial coverage.	3 / 3
Completeness	Explicitly states what it does (migration best practices for the listed operations) and when to use it via 'Use when planning or implementing database schema changes', satisfying both what AND when; not 2 because the trigger is explicit, not implied.	3 / 3
Trigger Term Quality	Uses natural terms a user would actually say ('database migration', 'schema changes', 'rollbacks', 'zero-downtime deployments') with good coverage; not below 3 because it avoids jargon-only phrasing.	3 / 3
Distinctiveness Conflict Risk	Database migrations with named ORMs/databases is a clear niche unlikely to trigger for unrelated skills; not 2 because the scope is specific rather than broadly overlapping.	3 / 3
	Total	12 / 12 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: 0c1d7be

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.