CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%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 body delivers excellent, executable code for every migration scenario and is mostly lean, but it is diluted by generic boilerplate sections, lacks explicit validation checkpoints in its destructive multi-step workflows (capping workflow clarity at 3), and keeps all ORM-specific detail inline with no reference-file structure.

Suggestions

Delete the generic filler sections ("Do not use this skill when", "Instructions", "Use this skill when") — they restate boilerplate and the description without adding migration-specific value.

Embed validation checkpoints in the destructive multi-phase workflows: verify row counts or backfill completeness before dropping the old column in the rename flow and between blue-green phases, instead of limiting verification to the single checkpoint-rollback example and a bare "test on staging" bullet.

Split per-ORM migration syntax into one-level-deep reference files (e.g., references/sequelize.md, references/typeorm.md, references/prisma.md) and keep SKILL.md as a strategy-level overview that links to them.

DimensionReasoningScore

Conciseness

The code examples are lean and assume Claude's competence, but three sections are generic filler: "Do not use this skill when" ("The task is unrelated to database migration"), the "Instructions" section ("Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes."), and "Use this skill when" restating the description as bullets. That is more than minor trimmable over-explanation, so anchor 3 rather than 4; not 2 because ~90% of the body is tight, executable code rather than verbose prose.

3 / 5

Actionability

Fully executable, copy-paste-ready code with concrete run/rollback commands ("npx sequelize-cli db:migrate:undo", "npm run typeorm migration:revert", "npx prisma migrate deploy") covering the common cases: per-ORM table creation, add/rename/change columns, parameterized data transformation, transaction and checkpoint rollback, blue-green phases, and cross-dialect branching. The prose-only blue-green phases 2 and 4 are inherently application-side, not a guidance gap.

5 / 5

Workflow Clarity

Multi-phase workflows (rename steps 1-3, blue-green phases 1-5) are clearly sequenced and the checkpoint example embeds a verify-then-restore loop, but most destructive/batch workflows lack validation checkpoints — no backfill or row-count verification between blue-green phases, no check before dropping the old column in the rename flow. Per the rubric's cap for destructive database operations without validation, this lands at anchor 3, not 4.

3 / 5

Progressive Disclosure

No bundle files exist; everything is inline in one ~420-line file. Internal section headers ("## ORM Migrations", "## Rollback Strategies", "## Zero-Downtime Migrations") give good structure, but per-ORM syntax detail that could live in reference files is fully inlined and there are no references to signal. Anchor 3 — not 2 because the file is well-sectioned and navigable, not 4/5 because nothing is split out despite the volume.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%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.

A strong description: it states concrete capabilities in third person and pairs them with an explicit multi-trigger "Use when" clause. The only notable gap is that it stays generic on "across ORMs" rather than naming the specific ORMs the skill actually covers.

DimensionReasoningScore

Specificity

Lists several concrete actions — "execute database migrations across ORMs and platforms", "zero-downtime strategies, data transformation, and rollback procedures" — matching anchor 4. Not 5 because it never names the actual ORMs (Sequelize, TypeORM, Prisma) the skill covers; not 3 since it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both what ("Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures") and when ("Use when migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies") with concrete trigger phrases, matching the anchor-5 example pattern. Not 4 because the when-clause is explicit and multi-trigger rather than weakly specified.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "migrating databases", "changing schemas", "performing data transformations", "implementing zero-downtime deployment strategies". Missing the ORM names a user would naturally mention ("migrate from Sequelize to Prisma") and synonyms like "schema migration" or "backfill".

4 / 5

Distinctiveness Conflict Risk

"Database migrations" is a clear niche with distinct triggers (ORM migrations, schema changes, zero-downtime, rollback) and minimal overlap risk with adjacent skills such as general deployment or CI skills.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/database-migration/SKILL.md

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.