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 template placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit 'Use when...' guidance. It would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions such as 'Generates SQL migration files for schema changes including CREATE TABLE, ALTER TABLE, adding/removing columns, and index modifications'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to create database migrations, modify schema, add or remove columns, or generate .sql migration files'.
Include natural trigger term variations users would actually say: 'database migration', 'schema change', 'migrate table', 'add column migration', 'db migration script', 'ALTER TABLE'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('SQL migration generator', 'Backend Development') 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 only trigger terms listed are 'sql migration generator' repeated twice. It misses natural variations users would say like 'database migration', 'schema change', 'migrate database', 'ALTER TABLE', 'create migration', 'db schema', '.sql files', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'SQL migration' is somewhat specific to a niche (database schema migrations), which provides some distinctiveness. However, the lack of concrete actions and the vague 'Backend Development' category could cause overlap with other backend or database-related 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 instructional content. It repeatedly references 'sql migration generator' without ever defining what tool, framework, or approach to use, providing no code examples, no migration file formats, no CLI commands, and no validation steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples for at least one migration framework (e.g., Alembic for Python, knex for Node.js, golang-migrate for Go) with actual SQL migration file templates and CLI commands.
Define a clear multi-step workflow: create migration → write SQL up/down → validate syntax → apply to dev database → verify → commit, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actionable technical content such as naming conventions, rollback patterns, and common pitfalls.
Add references to separate files for advanced topics like zero-downtime migrations, data migrations vs. schema migrations, and framework-specific guides.
| 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, providing no executable or copy-paste-ready content. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequencing, and no validation checkpoints for what is inherently a multi-step, potentially destructive operation (database migrations). The phrase 'step-by-step guidance' is claimed but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic descriptions with no meaningful structure. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections that exist are purely cosmetic. | 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
3e83543
- 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.