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.06x

Quality

—

Does it follow best practices?

Impact

88%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with executable commands, complete SQL examples, and a well-validated migration workflow, but it is a monolithic inline document that does not use its bundle files (which are unimplemented placeholders) and explains some patterns Claude already knows.

Suggestions

Externalize large inline sections (the Error Handling table, Examples, and framework-specific command details) into reference files under references/ and link to them from SKILL.md so the body is a lean overview.

Either implement the placeholder scripts/assets (create_migration.py, migration_template.sql, etc.) and reference them in the workflow, or remove the unused bundle directories so navigation matches reality.

Trim concept explanations Claude already knows (the expand-contract phase narration and the shadow-table mechanism) to keep the body token-lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and actionable, but it explains patterns Claude already knows (the expand-contract phase narration, 'These tools create a shadow table, replicate changes, then swap atomically', and 'Use IF NOT EXISTS for CREATE operations to make migrations idempotent') and could be tightened.	2 / 3
Actionability	It provides framework-specific executable commands ('pg_dump --schema-only -f schema_before.sql', 'alembic revision --autogenerate -m "..."', 'npx prisma migrate dev --name ...') and complete copy-paste-ready SQL examples ('CREATE TYPE order_status AS ENUM (...)','ALTER TABLE orders ADD COLUMN status order_status').	3 / 3
Workflow Clarity	The 10-step sequence is clearly ordered with an explicit staging validation loop in step 6 (apply UP and verify, run tests, apply DOWN and verify original state, re-apply UP to confirm idempotency) plus an error-handling table for recovery, appropriate for destructive migration operations.	3 / 3
Progressive Disclosure	The body is a monolithic ~85-line document with all content inline and no links to bundle files; the scripts/ and assets/ directories hold only placeholder TODOs ('create_migration.py', 'migration_template.sql') that are never referenced from SKILL.md.	2 / 3
	Total	10 / 12 Passed

Description

80%

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 has strong natural trigger terms and explicit when-guidance, but its 'what' is vague and grammatically broken ('Process use when...'), padded with fluff ('comprehensive guidance and automation'), and written in second person rather than third.

Suggestions

Rewrite the opening in third person with concrete actions, e.g. 'Creates, validates, and executes database schema migrations with rollback support across PostgreSQL, MySQL, and MongoDB.'

Drop the fluff ('comprehensive guidance and automation') and instead name concrete capabilities (create, validate, execute, rollback migrations) so the 'what' earns a specificity score of 3.

Keep the trigger clause but phrase it in third person ('Use when the user asks to create or run migrations or manage schema versions') to avoid the second-person penalty.

Dimension	Reasoning	Score
Specificity	It names the domain ('database migrations', 'schema migration management') but offers only abstract action words ('Process', 'management', 'automation') with no concrete enumerated actions, and it is written in second person ('use when you need to'), which the rubric reduces by one.	1 / 3
Completeness	It states what the skill does ('This skill provides schema migration management...') and gives explicit when-guidance with both a 'use when you need to work with database migrations' clause and a 'Trigger with phrases like...' list, satisfying both required elements.	3 / 3
Trigger Term Quality	It explicitly enumerates natural trigger phrases a user would say ('create migration', 'run migrations', 'manage schema versions') alongside 'database migrations', giving good coverage of likely requests.	3 / 3
Distinctiveness Conflict Risk	The triggers are tightly scoped to database/schema migration work ('database migrations', 'schema migration management', 'manage schema versions') and unlikely to fire for unrelated skills, giving a clear niche.	3 / 3
	Total	10 / 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
Commit: 607d11b

Reviewed: 2 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.