managing-database-migrations

Process use when you need to work with database migrations. This skill provides schema migration management with comprehensive guidance and automation. Trigger with phrases like "create migration", "run migrations", or "manage schema versions".

1.28x

Quality

91%

Does it follow best practices?

Impact

85%

1.28x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

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

The body is exceptionally actionable with concrete commands, a clear validated workflow, and zero padding. Its one weakness is progressive disclosure: it ignores the provided bundle files and keeps everything inline.

Suggestions

Reference the bundled scripts in the relevant steps, e.g. 'Run scripts/validate_migration.py' in the validation step and 'Start from assets/migration_template.sql' when generating files.

Move the expand-contract and large-table guidance into a reference file and link to it from the Instructions section to slim the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is dense but high-signal: framework-specific commands and naming conventions with no padding explaining what a database or migration is, assuming Claude's competence throughout.	3 / 3
Actionability	It gives concrete executable commands (pg_dump --schema-only, alembic revision --autogenerate, npx prisma migrate dev), exact file-naming conventions, and a complete worked SQL example that is copy-paste ready.	3 / 3
Workflow Clarity	A numbered 10-step sequence includes an explicit validation checkpoint (step 6: apply UP, verify, apply DOWN, verify original state, re-apply UP) with feedback loops for destructive database operations.	3 / 3
Progressive Disclosure	The SKILL.md is a monolithic ~85-line body and never signals the bundled scripts/templates in scripts/ and assets/ (e.g. create_migration.py, migration_template.sql); content that could live in those references is inline.	2 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 answers both what and when with strong, natural trigger terms and low conflict risk. Its main weakness is specificity: it relies on trigger phrases to imply actions rather than listing concrete capabilities.

Suggestions

Replace trigger-derived actions with an explicit capability list, e.g. 'Create, validate, apply, and roll back database schema migrations'.

The opening 'Process use when...' reads as a truncated fragment; restate it as a clean third-person clause such as 'Manages database schema migrations...'.

Dimension	Reasoning	Score
Specificity	Names the domain ('schema migration management') and implies actions via trigger phrases ('create migration', 'run migrations', 'manage schema versions'), but does not explicitly list multiple concrete capabilities such as create/validate/rollback.	2 / 3
Completeness	It states what the skill does ('schema migration management with comprehensive guidance and automation') and gives an explicit when/trigger clause ('Trigger with phrases like...').	3 / 3
Trigger Term Quality	'create migration', 'run migrations', and 'manage schema versions' are natural terms a user would actually say, with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The database-migration niche with these specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-migration-manager/skills/managing-database-migrations/SKILL.md
Commit: 4c47e33

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.