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.
79
67%
Does it follow best practices?
Impact
99%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/framework-migration/skills/database-migration/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates specific capabilities and includes an explicit 'Use when' clause with relevant trigger terms. The main weakness is that the broad scope ('across ORMs and platforms') and some general terms like 'data transformations' could create overlap with other database or ETL-related skills. Overall, it follows the pattern of the good examples closely and would serve well for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Execute database migrations', 'zero-downtime strategies', 'data transformation', and 'rollback procedures'. Also mentions 'across ORMs and platforms' which adds specificity about scope. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute database migrations with zero-downtime strategies, data transformation, rollback procedures across ORMs) and 'when' (explicit 'Use when' clause covering migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'database migrations', 'schemas', 'data transformations', 'zero-downtime', 'rollback', 'ORMs', 'deployment strategies'. These cover common variations of how users would describe migration-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | While 'database migrations' and 'zero-downtime' are fairly distinct, terms like 'data transformations' and 'changing schemas' could overlap with general database management or ETL-focused skills. The scope is broad ('across ORMs and platforms') which increases potential conflict with ORM-specific or platform-specific skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable code examples across multiple ORMs and migration scenarios, which is its primary strength. However, it is excessively verbose — repeating the same basic 'create users table' pattern three times across ORMs and including boilerplate that Claude can generate on its own. The content would benefit greatly from condensing to key patterns, gotchas, and decision points rather than full migration file templates, and splitting detailed examples into referenced sub-files.
Suggestions
Condense ORM-specific sections to a comparison table of key differences (CLI commands, file naming conventions, gotchas) rather than showing nearly identical full migration files for each ORM.
Split detailed examples (data transformations, cross-database migrations, rollback strategies) into separate referenced files, keeping only a concise overview with links in the main skill.
Add explicit validation checkpoints to the data transformation workflow (e.g., verify row counts before dropping old columns) — currently destructive operations like removeColumn happen without verification.
Remove the 'When to Use This Skill' section — Claude can infer applicability from the content itself, and this adds tokens without actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with repetitive patterns across ORMs showing essentially the same 'create users table' migration three times. The 'When to Use This Skill' bullet list and basic ORM migration examples explain things Claude already knows. Much of this could be condensed to key patterns and gotchas rather than full boilerplate. | 1 / 3 |
Actionability | All code examples are fully executable with specific commands for running and rolling back migrations. Examples include complete migration files with proper imports, function signatures, and CLI commands. | 3 / 3 |
Workflow Clarity | The zero-downtime section shows a clear multi-phase sequence (Phases 1-5), and the checkpoint-based rollback includes verification. However, most workflows lack explicit validation checkpoints — the data transformation section processes records without verifying success counts, and the column rename workflow has implicit steps ('Step 2: Update application') without validation gates. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of code examples with no references to external files. At ~300+ lines, the ORM-specific examples, cross-database migrations, and data transformation patterns should be split into separate reference files with a concise overview in the main skill. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
27a7ed9
- Reviewed
Table of Contents
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.