CtrlK
BlogDocsLog inGet started
Tessl Logo

database-migration

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

50

Quality

56%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/database-migration/SKILL.md

The canonical home for this skill is database-migration in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 content provides substantial executable, ORM-specific migration code with run/rollback commands, making it reasonably actionable. However, it is hurt by repeated verbose patterns, the absence of validation checkpoints for destructive migrations, and a Resources section that references bundle files which do not exist.

Suggestions

Move the bulk code examples into the referenced files (references/schema-migration.md, references/rollback-strategies.md, etc.) and keep SKILL.md as a concise overview — and ensure those files actually exist, fixing the inconsistent "resources/" vs "references/" path on line 23.

Add explicit validation checkpoints to destructive/batch workflows (e.g. run migrations on staging, verify row counts/backfill completeness, then proceed), with a validate→fix→retry feedback loop, to lift workflow clarity above 3.

Tighten repeated Sequelize up/down boilerplate and remove narration of basic steps ("Get all records", "Copy and transform data") that Claude already infers from the code.

DimensionReasoningScore

Conciseness

The body is mostly executable code (efficient) but repeats near-identical Sequelize up/down patterns across many sections and includes redundant narration ("// Get all records", "// Copy and transform data", "// Handle differences") that Claude does not need. It is mostly efficient with some tightening possible, matching the 3 anchor rather than the lean 5.

3 / 5

Actionability

Most sections give executable code with explicit run/rollback commands (e.g. "npx sequelize-cli db:migrate", "npm run typeorm migration:run", "npx prisma migrate deploy"), covering common cases well. It is not a 5 because Prisma rollback/down is omitted and a few examples (cross-database, checkpoint rollback) are partial.

4 / 5

Workflow Clarity

This is a destructive/batch database-migration skill, yet the multi-step sections (renaming columns, type changes, blue-green deploys) lack explicit validation checkpoints or feedback loops; the rubric caps such skills at 3. It is above 2 because sequences are present, but the missing validate-then-proceed gating prevents a higher score.

3 / 5

Progressive Disclosure

The body inlines ~400 lines of examples that clearly belong in reference files, and the Resources section lists files (references/*.md, assets/*, scripts/*) that do not exist in the skill directory; line 23 also references a non-existent "resources/implementation-playbook.md" with an inconsistent path prefix. Broken/missing bundle files plus inlined bulk content match the 2 anchor (minimal structure, references buried/invalid).

2 / 5

Total

12

/

20

Passed

Description

58%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.

The description states a clear, specific scope with concrete ORM names and migration strategies, giving it solid specificity and distinctiveness. Its main weakness is the missing explicit "Use when..." trigger clause and limited natural trigger phrasing, which caps both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when migrating between ORMs, transforming database schemas, or planning zero-downtime database deployments."

Broaden trigger terms with natural user phrasings and synonyms (e.g. "database migration", "schema change", "migrate to Prisma/TypeORM", ".sql migration files").

Consider mentioning concrete artifacts users reference (migration files, schema versions) to raise specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions — "database schema and data migrations", "rollback strategies", "zero-downtime deployments" — with only minor coverage gaps (e.g. no mention of seeding or version control of schemas). It is above a 3 (which would name only 1-2 actions) but does not reach 5 because the action list, while good, is not exhaustive.

4 / 5

Completeness

It has a clear "what" (master schema/data migrations across ORMs with rollback and zero-downtime) but no explicit "when"/"Use when" clause, which per the rubric caps completeness at 3. A 4 would require both a what and an explicit when, which is not present here.

3 / 5

Trigger Term Quality

Relevant keywords are present (ORM, Sequelize, TypeORM, Prisma, migration, rollback, zero-downtime) but it lacks the natural phrases a user would actually say and common synonyms/file types, and there is no "Use when..." trigger clause. It sits at 3 ("some relevant keywords but missing common variations") rather than 4 because several natural trigger terms are absent.

3 / 5

Distinctiveness Conflict Risk

Naming concrete ORMs (Sequelize, TypeORM, Prisma) plus "zero-downtime deployments" carves a fairly distinct niche with only minor overlap risk against general migration or ORM skills. It is not a 5 because the phrase "database schema and data migrations" alone could still overlap with broader DB-admin skills.

4 / 5

Total

14

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.