database-migration

Master database schema and data migrations across ORMs (Sequelize, TypeORM, Prisma), including rollback strategies and zero-downtime deployments.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/database-migration/SKILL.md

Quality

Content

50%Scale 1-5

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 three ORMs with good coverage of migration scenarios including rollbacks and zero-downtime strategies. However, it is overly verbose for Claude's knowledge level — basic table creation migrations don't need full examples for each ORM. The workflow clarity suffers from missing validation checkpoints on destructive operations, and the progressive disclosure is undermined by referencing non-existent bundle files while inlining too much content.

Suggestions

Drastically reduce boilerplate ORM examples (e.g., basic table creation) and focus only on non-obvious patterns like zero-downtime column renames and cross-database differences — Claude already knows how to write basic Sequelize/TypeORM/Prisma migrations.

Add explicit validation checkpoints to destructive workflows: e.g., after dropping a column, verify row counts match expectations; before removing backup tables, confirm data integrity.

Either provide the referenced bundle files (orm-switching.md, schema-migration.md, etc.) or remove the references — phantom references reduce trust in the skill.

Replace the vague Instructions section ('Clarify goals, constraints, and required inputs') with a concrete decision tree: e.g., 'If zero-downtime required → use Blue-Green pattern (Phase 1-5 below); If rollback critical → wrap in transaction.'

Dimension	Reasoning	Score
Conciseness	The skill is significantly verbose. It includes extensive code examples for basic ORM migration patterns that Claude already knows well (Sequelize, TypeORM, Prisma table creation). The description at the top repeats the frontmatter. Many examples are boilerplate that don't add unique value. The 'Do not use this skill when' section is trivially obvious.	2 / 5
Actionability	The skill provides concrete, executable code examples with run commands for each ORM. The migration patterns are copy-paste ready with realistic scenarios (renaming columns, changing types, data transformations). Minor gap: the Instructions section is vague ('Clarify goals, constraints, and required inputs') rather than actionable.	4 / 5
Workflow Clarity	The zero-downtime section outlines a clear multi-phase sequence (Phases 1-5), and the checkpoint-based rollback includes verification. However, most workflows lack explicit validation checkpoints — the renaming columns example says 'Step 2: Update application' without verification. For destructive operations like dropping columns and tables, there are insufficient validation gates, capping this at 3.	3 / 5
Progressive Disclosure	The Resources section references multiple external files (orm-switching.md, schema-migration.md, etc.) which is good structure, but none of these files exist in the bundle. The main file itself is ~300 lines with extensive inline code that could be split into referenced files. The reference to 'resources/implementation-playbook.md' in Instructions also doesn't exist.	3 / 5
	Total	12 / 20 Passed

Description

52%Scale 1-5

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 identifies a clear domain (database migrations) and names specific technologies (Sequelize, TypeORM, Prisma), which aids in trigger matching and distinctiveness. However, it lacks a 'Use when...' clause entirely, and the leading verb 'Master' is aspirational rather than action-oriented, making it unclear what concrete actions the skill performs. Adding explicit trigger guidance and replacing vague language with specific actions would significantly improve selection accuracy.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user needs to create, run, or rollback database migrations, or asks about schema changes with Sequelize, TypeORM, or Prisma.'

Replace 'Master' with concrete action verbs describing what the skill does, e.g., 'Generates, applies, and rolls back database schema and data migrations across Sequelize, TypeORM, and Prisma.'

Include additional natural trigger terms such as 'migration files', 'schema changes', 'db migrate', and 'ORM migrations' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (database migrations) and lists specific ORMs (Sequelize, TypeORM, Prisma), and mentions rollback strategies and zero-downtime deployments, but the verb 'Master' is vague and doesn't describe concrete actions like 'generate migration files', 'apply schema changes', or 'write rollback scripts'.	3 / 5
Completeness	Provides a partial 'what' (schema and data migrations, rollback strategies, zero-downtime deployments) but has no 'when' clause at all. The absence of a 'Use when...' clause caps this at 3 per guidelines, and the 'what' is also somewhat vague with 'Master' as the leading verb, placing it at 2.	2 / 5
Trigger Term Quality	Includes good natural keywords like 'database schema', 'data migrations', 'Sequelize', 'TypeORM', 'Prisma', 'rollback', and 'zero-downtime deployments'. Missing some common variations like 'migration files', 'schema changes', 'migrate database', 'db migration', or 'ORM'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct by specifying database migrations with specific ORMs and deployment strategies. Minor overlap risk with general database skills or ORM-specific skills, but the combination of migration focus plus named ORMs plus zero-downtime makes it reasonably distinguishable.	4 / 5
	Total	13 / 20 Passed

Validation

90%

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 — 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

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/database-migration/SKILL.md
Commit: 57c135b

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