database-migrations-sql-migrations

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

Quality

51%

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

42%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 is well-structured and reasonably concise but provides only generic, non-executable guidance with no SQL examples or feedback loops, and it references a playbook file that is missing from the bundle.

Suggestions

Add at least one concrete, executable SQL migration example (e.g., an expand-contract column rename with validation queries) instead of deferring all detail to the missing playbook.

Provide the referenced resources/implementation-playbook.md or remove the broken reference so navigation actually resolves.

Insert explicit validation checkpoints with a feedback loop (run pre-checks -> apply -> verify -> rollback if failed) into the migration workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with organized sections, but the 'You are a SQL database migration expert...' intro and the repeated 'production-ready' phrasing restate the description and could be tightened, matching anchor 3.	3 / 5
Actionability	Instructions are high-level hints ('Apply relevant best practices and validate outcomes') with no SQL, code, or concrete commands, and the detailed examples are deferred to a referenced file that does not exist, fitting anchor 2.	2 / 5
Workflow Clarity	The numbered Output Format gives a rough sequence including validation and rollback items, but there is no validate->fix->retry feedback loop; for destructive/batch database operations this caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Section structure is reasonable and references are clearly signaled, but the single referenced file (resources/implementation-playbook.md) is not present, so the one-level-deep reference does not resolve, landing at anchor 3.	3 / 5
	Total	11 / 20 Passed

Description

61%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 clearly states the domain and target engines but omits any explicit 'Use when' trigger guidance, which caps completeness. It is reasonably specific and distinctive but lacks concrete action verbs.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when performing schema migrations, zero-downtime deploys, or rollback planning for PostgreSQL/MySQL/SQL Server').

Replace the noun-heavy phrasing with concrete action verbs (e.g., 'Generate, validate, and roll back SQL migrations').

Include common synonyms such as 'schema migrations' and tool names users may mention (Flyway, Liquibase, Alembic).

Dimension	Reasoning	Score
Specificity	Names the domain ('SQL database migrations') plus one concrete aspect ('zero-downtime strategies') and three engines, but uses no action verbs and is not comprehensive, matching anchor 3.	3 / 5
Completeness	The 'what' is clear but there is no 'Use when...' or equivalent trigger clause, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('SQL database migrations', 'zero-downtime', 'PostgreSQL', 'MySQL', 'SQL Server') with good coverage; a few synonyms like 'schema migration' are missing, so just above anchor 3.	4 / 5
Distinctiveness Conflict Risk	The zero-downtime SQL migration niche for three named engines is mostly distinct with only minor overlap risk against related DB skills; not anchor 5 because the trigger phrasing is not maximally distinctive.	4 / 5
	Total	14 / 20 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: 3eff4af

Reviewed: 1 day 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.