sql-migration-generator

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sql-migration-generator

Sql Migration Generator - Auto-activating skill for Backend Development. Triggers on: sql migration generator, sql migration generator Part of the Backend Development skill category.

19%

Overall

Validation — 69%

Implementation — 0%

Activation — 7%

SKILL.md

Review

Evals

Validation

69%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Implementation

This skill is essentially an empty placeholder with no actionable content. It describes what a SQL migration generator skill would theoretically do but provides zero actual guidance, code examples, migration patterns, or workflow steps. The entire content could be replaced with a single sentence without losing any information.

Suggestions

Add concrete, executable code examples for generating migrations in at least one framework (e.g., Alembic for Python, Knex for Node.js, or golang-migrate for Go)

Define a clear workflow with validation steps: create migration -> review SQL -> test on dev -> apply -> verify -> document rollback procedure

Include specific migration patterns: adding columns, creating indexes, handling data migrations, foreign key constraints with examples

Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual migration syntax and commands

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about SQL migrations.	1 / 3
Actionability	There is zero concrete guidance - no code examples, no specific commands, no actual migration syntax or patterns. The skill describes what it claims to do rather than providing any executable instructions.	1 / 3
Workflow Clarity	No workflow is defined at all. SQL migrations involve critical multi-step processes (create migration, test, apply, rollback) but none of these steps are documented or sequenced.	1 / 3
Progressive Disclosure	The content is a monolithic block of vague descriptions with no structure pointing to detailed materials, examples, or references. There's nothing to progressively disclose because there's no actual content.	1 / 3
	Total	4 / 12 Passed

Activation

This description is essentially a placeholder with no substantive content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The duplicate trigger term suggests auto-generation without human refinement.

Suggestions

Add specific actions the skill performs, e.g., 'Generates SQL migration files for schema changes, creates up/down migrations, handles table creation, column modifications, and index management'

Include a 'Use when...' clause with natural trigger terms like 'database migration', 'schema change', 'alter table', 'add column', 'create table migration', 'db versioning'

Specify supported databases or frameworks if applicable (e.g., PostgreSQL, MySQL, Rails migrations, Flyway) to improve distinctiveness

Dimension	Reasoning	Score
Specificity	The description only names the skill 'Sql Migration Generator' without describing any concrete actions. There are no specific capabilities listed like 'generates migration files', 'creates schema changes', or 'handles database versioning'.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause. The 'Triggers on' section is redundant and doesn't provide meaningful guidance on when to select this skill.	1 / 3
Trigger Term Quality	The trigger terms are just the skill name repeated twice ('sql migration generator, sql migration generator'). Missing natural variations users would say like 'database migration', 'schema change', 'alter table', 'db versioning', or 'migration script'.	1 / 3
Distinctiveness Conflict Risk	While 'SQL migration' is a somewhat specific domain, the lack of detail about what kind of migrations (schema, data, rollback) or which database systems could cause overlap with general database or SQL skills.	2 / 3
	Total	5 / 12 Passed

Reviewed

14 days ago

Table of Contents

Validation Implementation Activation

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.