database-migration

Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies.

1.08x

Quality

—

Does it follow best practices?

Impact

92%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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, copy-paste-ready migration code, but it is verbose with redundant examples, lacks validation checkpoints in its destructive/batch workflows, and inlines content that its own Resources section claims lives in non-existent bundle files.

Suggestions

Add explicit validation/verification checkpoints to destructive and batch workflows — e.g., after the record-loop data migration and between each zero-downtime phase, assert expected row counts or schema state before proceeding.

Consolidate the three near-identical ORM "create users" examples and redundant Sequelize migration blocks into a single representative example plus a compact per-ORM command table to cut tokens.

Either create the referenced bundle files (references/*.md, assets/*, scripts/test-migration.sh) and move the detailed patterns into them, or remove the Resources section so navigation does not point at missing files.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy and avoids explaining concepts Claude already knows, but it is verbose: three near-identical ORM "create users" examples and several repeated Sequelize migration blocks (e.g. "Adding Columns", "Renaming Columns", "Changing Column Types") could be consolidated; not score 3 because not every token earns its place.	2 / 3
Actionability	Examples are fully executable JavaScript/TypeScript/Prisma with concrete run and rollback commands such as "npx sequelize-cli db:migrate" and "npx sequelize-cli db:migrate:undo", making them copy-paste ready rather than pseudocode (score 2) or abstract direction (score 1).	3 / 3
Workflow Clarity	Multi-step flows are sequenced ("Step 1: Add new column", "Phase 1... Phase 5") and the checkpoint rollback verifies ("SELECT COUNT(*) ... WHERE new_field IS NULL"), but core destructive/batch workflows like the record-loop data migration and the zero-downtime phases lack explicit validation checkpoints, capping this at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	A Resources section clearly signals references ("references/orm-switching.md", "assets/schema-migration-template.sql", "scripts/test-migration.sh"), but those bundle files do not exist on disk and the detailed migration content that belongs in them is inlined as a ~400-line wall in SKILL.md; not score 3 because content that should be separate is inline, and not score 1 because organization and signaling are present rather than nested/poor.	2 / 3
	Total	9 / 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.

The description is concise, third-person, and clearly answers both what the skill does and when to use it with natural trigger terms. It is a strong, distinct description with no over-claims.

Dimension	Reasoning	Score
Specificity	It lists several concrete actions — "Execute database migrations across ORMs and platforms", "zero-downtime strategies, data transformation, and rollback procedures" — matching the multiple-specific-actions anchor rather than the partial (score 2) or vague (score 1) anchors.	3 / 3
Completeness	It states what the skill does ("Execute database migrations...") and gives an explicit "Use when migrating databases, changing schemas..." trigger clause, satisfying both what and when; not score 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	The "Use when" clause surfaces natural phrases a user would say — "migrating databases, changing schemas, performing data transformations, ... zero-downtime deployment strategies" — giving good coverage rather than the limited (score 2) or jargon-only (score 1) levels.	3 / 3
Distinctiveness Conflict Risk	Database migration with zero-downtime/rollback framing is a clear niche with distinct triggers unlikely to overlap unrelated skills; it is far more specific than the overlapping (score 2) or generic (score 1) anchors.	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
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: e9f9b67

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