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.
35
3%
Does it follow best practices?
Impact
93%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/sql-migration-generator/SKILL.mdQuality
Discovery
7%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 essentially a placeholder that repeats the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SQL migration files for schema changes including CREATE TABLE, ALTER TABLE, adding/removing columns, and index modifications.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create database migrations, modify schema, add columns, change tables, or generate .sql migration files.'
Expand trigger terms to include natural variations users would say: 'database migration', 'schema change', 'migrate table', 'add column migration', 'ALTER TABLE', 'CREATE TABLE', 'migration file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('SQL migration generator') but describes no concrete actions. There are no specific capabilities listed such as 'generates migration files', 'creates ALTER TABLE statements', or 'handles schema changes'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'sql migration generator' repeated twice. Missing natural variations users would say like 'database migration', 'schema change', 'migrate database', 'ALTER TABLE', 'create migration', '.sql files', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'SQL migration generator' is somewhat specific to a niche (database migrations), which provides some distinctiveness. However, the lack of detail means it could overlap with general database skills or other backend development skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual technical content. It repeatedly references 'sql migration generator' without ever defining what tool, language, or approach to use, and provides no code, commands, examples, or workflows. It would be entirely unhelpful to Claude in performing any SQL migration task.
Suggestions
Add concrete, executable code examples for at least one migration tool (e.g., Alembic for Python, Knex for Node.js, golang-migrate for Go) showing how to create and run a migration.
Define a clear multi-step workflow: generate migration file → write up/down SQL → validate schema → apply migration → verify, with explicit validation checkpoints and rollback instructions.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical guidance, patterns, and best practices for writing safe SQL migrations.
Add specific examples of common migration patterns (add column, rename table, add index, data migration) with copy-paste-ready SQL and CLI commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'sql migration generator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no SQL examples, no migration commands, no code snippets, no specific tools (e.g., Flyway, Alembic, knex migrations). The skill describes rather than instructs and provides nothing executable. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. SQL migrations are inherently multi-step (create migration, write SQL, validate, apply, rollback strategy) and none of these steps are mentioned, let alone sequenced with validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed guides, no separation of quick-start vs. advanced content, and the sections that exist are boilerplate with no real information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
3076d78
- Reviewed
Table of Contents
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.