Name: database-migrations-sql-migrations
Rating: 49.6 (1 reviews)
Author: administrakt0r

database-migrations-sql-migrations

SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.

Quality

53%

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

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

Quality

Content

46%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 cleanly sectioned and concise enough, but it offers almost no executable guidance and frames a deliverable list as a workflow without validation checkpoints for destructive migration operations.

Suggestions

Replace the generic Instructions with at least one concrete executable pattern, e.g., an expand-contract migration snippet (add column -> backfill -> switch -> drop) with real SQL for PostgreSQL/MySQL/SQL Server.

Turn the Output Format into a true sequenced workflow with explicit validation checkpoints (e.g., run pre-migration checks, apply, validate row counts, only then promote, else roll back), including a validate->fix->retry loop.

Remove the redundant 'Context' and 'Resources' sections (they restate the Overview) and either supply the referenced 'implementation playbooks' as bundle files or drop the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but the role preamble, the 'Context' section, and the one-line 'Resources' section each restate the Overview, and the Instructions are generic template bullets that could be trimmed.	3 / 5
Actionability	Guidance is largely abstract: the Instructions are generic ('Clarify goals', 'Apply relevant best practices') and the Output Format names deliverables without any executable SQL, commands, or concrete expand-contract/rollback patterns, and it defers 'detailed examples' to nonexistent playbooks.	2 / 5
Workflow Clarity	The Output Format gives a rough sequence of deliverables (analysis, plan, scripts, validation, rollback) but no validate->fix->retry checkpoint, and because database migrations are destructive/batch operations the missing validation loop caps this score at 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections and no bundle files, which suits a single-file overview, but the inline mention of 'implementation playbooks' is a dangling reference to files that do not exist, a minor organization gap.	4 / 5
	Total	12 / 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 is specific and well-targeted to a clear niche, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness and leaves it short of top-tier examples.

Suggestions

Add an explicit 'Use when...' clause naming the concrete trigger phrases a user would say (e.g., 'Use when planning zero-downtime schema changes, writing migration scripts, or designing rollback procedures for PostgreSQL/MySQL/SQL Server').

Lead with concrete action verbs (e.g., 'Generate', 'Validate', 'Roll back') instead of 'strategies' and 'plans' to lift specificity above the midpoint.

Include common synonyms users say ('schema changes', 'migration scripts', 'deploy migrations') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus concrete focus areas ('zero-downtime strategies', 'data integrity', 'rollback plans') and three specific engines, but states deliverables/strategies rather than executable action verbs, so it stops at naming 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The 'what' is clear (zero-downtime SQL migrations with rollback focus), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural user phrasing ('SQL database migrations', 'zero-downtime', 'rollback plans', PostgreSQL/MySQL/SQL Server) with good coverage; a few common synonyms like 'schema changes' or 'migration scripts' are missing, so it falls just short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (zero-downtime migrations for three named engines) that is mostly distinct, with only minor overlap risk against general SQL/database skills; not quite the minimal-conflict anchor because triggers overlap with broader DB tooling.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/database-migrations-sql-migrations/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.