CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

database-migrations

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/database-migrations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable, tool-specific migration guidance with exemplary validation gates and checklists on its risky workflows. Its weaknesses are redundancy (duplicate activation sections, timeline restating phases), one non-executable batch code block, and broken references to example files that are absent from the bundle.

Suggestions

Merge the duplicate "When to Activate" and "When to Use This Skill" bullet lists into a single section, and cut the Timeline Example that restates the phase list.

Create the referenced examples/postgres-add-column.sql and examples/postgres-column-rename.sql files, or remove the links — they currently point to nonexistent paths.

Fix the batched backfill example to use a CALL-able PROCEDURE (or an app-side loop) since COMMIT inside a DO block fails with invalid transaction termination.

Consider moving the per-ORM sections (Prisma, Drizzle, Django, golang-migrate) into one-level-deep reference files so SKILL.md stays an overview.

DimensionReasoningScore

Conciseness

The content is mostly dense and code-first, but "When to Activate" and "When to Use This Skill" are near-duplicate five-bullet lists, and the "Timeline Example" restates the phase description immediately above it. This matches anchor 3 (mostly efficient, some content that could be tightened) better than 4, where trimming would be minor.

3 / 5

Actionability

Nearly all guidance is copy-paste-ready: ALTER TABLE variants with lock caveats, concurrent index DDL, expand-contract SQL, complete Django migration code, and per-tool CLI workflows. The batched DO $$ ... COMMIT ... END $$ block is not executable as written (COMMIT cannot appear inside a DO block — it requires a PROCEDURE), and rename Step 2 is prose-only, so minor gaps keep it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The expand-contract rename is a 7-step sequence with an explicit validation gate ("Require zero mismatches before switching reads"), retry feedback ("retry failed batch transactions"), a pre-flight safety checklist, and documented rollback plans — the database/batch feedback-loop requirement is fully met, matching anchor 5. It is not 4 because the risky workflows (backfill, cutover, contract) all carry explicit checkpoints.

5 / 5

Progressive Disclosure

Section headers are clear, but the ~420-line body inlines per-ORM reference material that could live in separate files, and the two example links (examples/postgres-add-column.sql, examples/postgres-column-rename.sql) point to files that do not exist in the bundle, so navigation fails at exactly those references. This fits anchor 3 (structure present but organization/reference gaps) rather than 4, where gaps would be minor.

3 / 5

Total

15

/

20

Passed

Description

78%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 with concrete action areas, broad natural trigger terms, an explicit 'Use when' clause, and a well-defined niche with named tools. Its main weakness is that the when-clause covers only planning/implementing, leaving troubleshooting and review scenarios unclaimed.

DimensionReasoningScore

Specificity

Lists several specific action areas — "schema changes, data migrations, rollbacks, and zero-downtime deployments" — plus named tools (PostgreSQL, MySQL, Prisma, Drizzle, Django, TypeORM, golang-migrate), but "best practices for" is generic framing rather than a concrete action verb, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ("Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments...") and when ("Use when planning or implementing database schema changes"). The when-clause is narrower than the what — it omits troubleshooting or reviewing migrations — so it matches anchor 4 (both present, when could be more specific) rather than 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say — "database migration", "schema changes", "rollbacks", "zero-downtime", and six tool names — but misses common variations like "backfill", "add a column", "ALTER TABLE", or "migration failed". Good coverage, a few natural terms missing, so anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (database migrations) with specific engines and ORM tools named, giving distinct triggers and minimal conflict risk with other skills — a clean match for anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 possibly missing (examples/postgres-add-column.sql, examples/postgres-column-rename.sql)

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

.kiro/skills/database-migrations/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.