database-migrations-sql-migrations

SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server

Quality

46%

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-migrations-sql-migrations/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is well-structured and concise but offers almost no actionable, migration-specific guidance in SKILL.md itself, and its single external reference target is missing from the bundle.

Suggestions

Add at least one concrete, executable example in SKILL.md (e.g. an expand-contract migration SQL snippet with a corresponding rollback) rather than only abstract instructions.

Replace the generic instruction bullets with a real sequenced migration workflow that includes explicit validation checkpoints (pre-checks, apply, post-checks, rollback-on-failure).

Create the referenced resources/implementation-playbook.md or remove the dangling reference so progressive disclosure points to a real file.

Dimension	Reasoning	Score
Conciseness	The body is short and sectioned, but the intro paragraph and closing line restate the description, and the 'Use/Do not use this skill when' sections are generic boilerplate — mostly efficient with some redundancy that could be tightened.	2 / 3
Actionability	Instructions are abstract boilerplate ('Clarify goals...', 'Apply relevant best practices and validate outcomes') with no concrete SQL, commands, or migration-specific steps; the only concrete material is offloaded to a referenced file, matching 'vague or abstract; describes rather than instructs'.	1 / 3
Workflow Clarity	The Output Format lists an ordered set of deliverables and mentions validation/rollback, but the actual instruction sequence has no explicit validation checkpoints or feedback loops for destructive migration work, capping clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized and the body points one level deep to resources/implementation-playbook.md, but that referenced file does not exist in the bundle, so the navigation is broken rather than genuinely progressive.	2 / 3
	Total	7 / 12 Passed

Description

57%

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 specific and distinctive about its SQL migration niche but omits an explicit 'when to use' trigger clause and lacks breadth of action verbs and common keyword variations.

Suggestions

Add an explicit 'Use when...' clause naming trigger situations (e.g. schema changes, adding indexes to large tables, migration rollback planning).

Include more concrete action verbs (create, rollback, validate, expand/contract) rather than only naming the strategy.

Add common user-facing variations like 'schema migrations', 'database schema changes', and framework names (Alembic, Flyway, Liquibase) to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('SQL database migrations') and a concrete strategy ('zero-downtime strategies') plus three specific engines, but does not list multiple concrete actions (e.g. create scripts, rollback, validate) — closest to 'names domain and some actions, not comprehensive'.	2 / 3
Completeness	Clearly states what the skill does but lacks any explicit 'Use when...' trigger clause in the description, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('SQL database migrations', 'PostgreSQL, MySQL, SQL Server') but misses common variations a user would say ('schema changes/migrations', 'Alembic/Flyway/Liquibase'), matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The narrow zero-downtime-migration niche tied to three named database engines is a clear, distinct trigger space unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/database-migrations-sql-migrations/SKILL.md
Commit: e63f7dd

Reviewed: about 4 hours 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.