tdg-personal/database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
80
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%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 with excellent specificity, naming concrete actions and a comprehensive list of supported technologies. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The domain is well-defined and distinctive, making it unlikely to conflict with other skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about database migrations, schema evolution, migration rollbacks, or zero-downtime database deployments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema changes, data migrations, rollbacks, and zero-downtime deployments' along with specific technologies (PostgreSQL, MySQL, Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities and technologies, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'database migration', 'schema changes', 'rollbacks', 'zero-downtime', plus specific ORM and database names that users would naturally mention. Good coverage of both general and specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on database migrations. The combination of migration-specific actions and named ORMs/databases makes it very unlikely to conflict with other skills like general database querying or application deployment skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent concrete examples across multiple tools and databases. The workflow clarity is strong with explicit safety checklists, validation steps, and the expand-contract pattern. However, the skill is far too long for a single SKILL.md — the six ORM-specific sections should be split into separate reference files, keeping only the core principles, safety checklist, and PostgreSQL patterns in the main file.
Suggestions
Split ORM-specific sections (Prisma, Drizzle, Kysely, Django, golang-migrate) into separate files (e.g., prisma.md, django.md) and link to them from a concise 'Tool-Specific Guides' section in SKILL.md.
Move the anti-patterns table and zero-downtime strategy into a separate reference file (e.g., PATTERNS.md) to keep the main skill focused on the core checklist and most common PostgreSQL patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but quite long (~300+ lines). Some sections like the Kysely programmatic migrator and the full Prisma schema example add bulk that could be offloaded to reference files. However, most content is genuinely useful and not explaining things Claude already knows. | 2 / 3 |
Actionability | Excellent actionability throughout — every ORM/tool section includes executable CLI commands and real SQL/code examples. The PostgreSQL patterns show concrete GOOD/BAD comparisons with actual SQL. Migration files are copy-paste ready. | 3 / 3 |
Workflow Clarity | The zero-downtime expand-contract pattern is clearly sequenced with phases and a timeline example. The safety checklist provides explicit validation checkpoints. The rename column example shows a clear 4-step sequence with migration numbering. Batch operations include progress tracking and exit conditions. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The PostgreSQL patterns, six different ORM/tool sections, zero-downtime strategy, and anti-patterns table are all inline. This would benefit enormously from splitting ORM-specific sections into separate files with a concise overview linking to them. | 1 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents