tessl i github:wshobson/agents --skill database-migrationExecute 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.
Validation
88%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
Implementation
77%This is a comprehensive and highly actionable skill with excellent executable code examples across multiple ORMs and clear multi-step workflows with validation checkpoints. The main weaknesses are moderate verbosity (generic best practices, obvious use cases) and a somewhat monolithic structure that could benefit from splitting detailed examples into reference files.
Suggestions
Remove or significantly trim the 'When to Use This Skill', 'Best Practices', and 'Common Pitfalls' sections as they contain information Claude already knows
Move detailed examples (Cross-Database Migrations, Complex Data Migration) to reference files and keep only the most common patterns in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'When to Use This Skill' section that Claude can infer, and the 'Best Practices' and 'Common Pitfalls' sections contain generic advice Claude already knows. The code examples are appropriately detailed without excessive explanation. | 2 / 3 |
Actionability | Provides fully executable code examples across multiple ORMs (Sequelize, TypeORM, Prisma) with complete migration files, specific CLI commands for running/rolling back, and concrete patterns for complex scenarios like zero-downtime column renames. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit phases (e.g., Blue-Green deployment has 5 numbered phases). Transaction-based and checkpoint-based rollback strategies include validation steps and error recovery patterns. The column rename example shows clear step-by-step progression. | 3 / 3 |
Progressive Disclosure | References external files appropriately in the Resources section, but the main content is quite long (~350 lines) with some sections that could be split into separate reference files (e.g., Cross-Database Migrations, Complex Data Migration examples). The structure is good but content density is high. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, uses natural trigger terms that users would actually say, includes an explicit 'Use when...' clause, and carves out a distinct niche around database migrations that won't conflict with other database-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Execute database migrations', 'zero-downtime strategies', 'data transformation', and 'rollback procedures'. Also mentions working 'across ORMs and platforms' which adds specificity. | 3 / 3 |
Completeness | Clearly answers both what (execute migrations with zero-downtime strategies, data transformation, rollback procedures) AND when (explicit 'Use when...' clause covering migrating databases, changing schemas, data transformations, zero-downtime deployment). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'database migrations', 'migrating databases', 'changing schemas', 'data transformations', 'zero-downtime deployment', 'rollback'. These cover common variations of how users would describe these tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on database migrations specifically, with distinct triggers like 'migrations', 'schemas', 'rollback', 'zero-downtime'. Unlikely to conflict with general database query skills or other development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
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.