CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

80%

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 ./skills/database-migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 shines on actionability with extensive executable migration examples, but it is capped on workflow clarity by missing explicit validate->fix->retry feedback loops for destructive operations, and its progressive disclosure is undermined by references to bundle files that do not exist.

Suggestions

Add an explicit validation feedback loop to the migration workflow (e.g., run migration on staging, verify row counts/schema, rollback on failure, retry) to lift workflow_clarity above the destructive-operation cap.

Create the referenced bundle files (references/orm-switching.md, schema-migration.md, data-transformation.md, rollback-strategies.md, assets/schema-migration-template.sql, assets/data-migration-script.py, scripts/test-migration.sh) or remove the dangling references.

Replace the generic boilerplate 'Instructions' section ('Clarify goals...', 'Apply relevant best practices...') with concrete, skill-specific steps to improve conciseness.

DimensionReasoningScore

Conciseness

Dense, executable code earns its tokens and concept-padding is minimal, but the generic 'Instructions' section ('Clarify goals...', 'Apply relevant best practices...') is boilerplate fluff and best practices/pitfalls are slightly redundant.

4 / 5

Actionability

Copy-paste-ready, fully executable migration code across Sequelize, TypeORM, and Prisma with explicit run/rollback commands covering the common scenarios (add/rename/type-change columns, data migration, rollback strategies).

5 / 5

Workflow Clarity

Multi-step sequences are clear (3-step rename, 5-phase blue-green), but this is a destructive/batch database-migration skill and the rubric caps workflow clarity at 3 when validation/verification feedback loops are absent; the opening 'Instructions' only say 'validate outcomes' generically rather than giving concrete validate->fix->retry checkpoints.

3 / 5

Progressive Disclosure

The body signals references/assets/scripts (orm-switching.md, schema-migration.md, etc.) but none of these bundle files actually exist in the skill directory, so the signaled one-level-deep references are dangling rather than navigable.

3 / 5

Total

15

/

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.

The description is strong: it states concrete capabilities and an explicit, trigger-rich 'Use when' clause, satisfying both what and when. Minor gains are possible by adding natural synonyms or file extensions as triggers.

DimensionReasoningScore

Specificity

Lists several concrete actions ('execute database migrations across ORMs and platforms', 'zero-downtime strategies, data transformation, and rollback procedures') with minor gaps in coverage versus a fully comprehensive 5.

4 / 5

Completeness

Clearly answers both 'what' (execute migrations across ORMs/platforms with strategies, transformation, rollback) and 'when' via an explicit 'Use when migrating databases, changing schemas...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-phrase coverage ('migrating databases', 'changing schemas', 'data transformations', 'zero-downtime deployment strategies') but missing common synonyms and file extensions like .sql or named ORM products as triggers.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (database migration) with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.