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.

Install with Tessl CLI

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

What are skills?

1.04x

Review — 3%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 93%

↑ 1.04x

Agent success when using this skill

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The repetitive trigger terms and boilerplate category information provide no value for skill selection.

Suggestions

Add specific actions the skill performs, e.g., 'Generates SQL migration files for schema changes including CREATE TABLE, ALTER TABLE, and index modifications'

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

Specify the context or frameworks supported (e.g., 'for PostgreSQL/MySQL' or 'compatible with Rails, Django, or raw SQL') to improve distinctiveness

Dimension	Reasoning	Score
Specificity	The description only states 'Sql Migration Generator' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'generates', 'creates', 'validates', or specific capabilities are mentioned.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of capabilities and no 'Use when...' clause or equivalent guidance for when to select this skill.	1 / 3
Trigger Term Quality	The triggers listed are just 'sql migration generator' repeated twice. This misses natural variations users would say like 'database migration', 'schema change', 'alter table', 'create migration', 'db schema', or 'migration file'.	1 / 3
Distinctiveness Conflict Risk	While 'SQL migration' is a somewhat specific domain, the lack of detail about what kind of migrations (schema changes, data migrations, rollbacks) or which databases/frameworks could cause overlap with general database or backend skills.	2 / 3
	Total	5 / 12 Passed

Implementation

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

This skill is essentially a placeholder with no actionable content. It describes what the skill should do in abstract terms but provides zero concrete guidance on SQL migration generation—no code examples, no migration syntax, no workflow steps, no tool-specific commands. Claude would gain nothing from this skill that it doesn't already know.

Suggestions

Add concrete, executable examples showing how to generate migrations for at least one framework (e.g., Alembic for Python, Knex for Node.js, or golang-migrate for Go)

Define a clear workflow: 1) Generate migration file, 2) Write up/down SQL, 3) Validate syntax, 4) Test migration, 5) Apply to database

Include example migration file templates with proper naming conventions and structure

Add validation checkpoints such as 'run migration in dry-run mode' or 'verify rollback works before committing'

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing specific about SQL migrations. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value.	1 / 3
Actionability	No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate a SQL migration or what the output looks like.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps for creating migrations, no validation checkpoints, and no guidance on migration ordering, rollbacks, or testing. The content is purely descriptive metadata.	1 / 3
Progressive Disclosure	The content is a flat, monolithic description with no structure for discovery. There are no references to detailed documentation, examples, or related files that would help Claude understand SQL migration patterns.	1 / 3
	Total	4 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

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