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.
80
71%
Does it follow best practices?
Impact
92%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 its broad scope ('across ORMs and platforms') and some general terms like 'data transformations' could create overlap with adjacent skills. Overall, it follows best practices and would perform well in 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). | 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
50%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 strategies, which is its primary strength. However, it is excessively verbose — much of the content is standard ORM boilerplate that Claude already knows, and the file reads more like a reference manual than a concise skill guide. The workflow clarity would benefit from explicit validation checkpoints in more of the migration examples, particularly for destructive operations like column removal and data transformations.
Suggestions
Drastically reduce the content by removing redundant ORM-specific 'create table' examples — keep one canonical example and reference ORM docs for others, or move ORM-specific examples to separate reference files.
Add explicit validation/verification steps to schema transformation and data migration workflows (e.g., 'Verify row counts match before dropping old column', 'Check for NULL values after data copy').
Move the bulk of code examples into referenced files (e.g., references/sequelize-migrations.md, references/typeorm-migrations.md) and keep SKILL.md as a concise overview with the key patterns and decision points.
Remove the 'When to Use This Skill', 'Best Practices', and 'Common Pitfalls' sections — these are generic advice Claude already knows and consume tokens without adding unique value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines, with extensive boilerplate code examples that repeat similar patterns (create table in Sequelize, TypeORM, Prisma). Much of this is standard ORM documentation that Claude already knows. The 'When to Use This Skill' section, 'Best Practices' bullet list, and 'Common Pitfalls' are largely things Claude can infer. The three separate ORM examples for creating a users table are redundant. | 1 / 3 |
Actionability | The code examples are fully executable and copy-paste ready with specific commands for running and rolling back migrations. Each example includes concrete file paths, complete function signatures, and CLI commands (e.g., `npx sequelize-cli db:migrate`, `npx prisma migrate deploy`). | 3 / 3 |
Workflow Clarity | The zero-downtime section shows a clear multi-phase sequence (Phases 1-5) and the checkpoint-based rollback includes verification steps. However, most migration workflows lack explicit validation checkpoints — for instance, the schema transformation examples don't include verification that the migration succeeded before proceeding. The data transformation example processes records one-by-one with no batch validation or error handling. | 2 / 3 |
Progressive Disclosure | The Resources section references external files (references/orm-switching.md, scripts/test-migration.sh, etc.) which is good, but the main file itself is a monolithic wall of code examples that could be split into separate reference files per ORM or per strategy. The inline content is far too long for a SKILL.md overview. | 2 / 3 |
Total | 8 / 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
- Dicklesworthstone/pi_agent_rust
- Commit
dad585c
- 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.