alembic-migration

Creates versioned Alembic migration scripts with tables, columns, primary keys, foreign keys, unique and functional constraints (e.g. case-insensitive uniqueness), and reference-data seeds, all derived from the entity model. Use when the user asks to "create a migration", "add a database migration", "write an Alembic migration", "add a column", "add a foreign key", "seed reference data", or mentions Alembic, schema migration, or database schema changes.

Quality

100%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

A tight, actionable skill body: concrete Alembic commands and SQLAlchemy type-mapping rules, a sequenced workflow with explicit verification and downgrade checkpoints, and cleanly organized sections pointing one level deep to repo documentation. It adds only what Claude would not already know.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what Alembic or migrations are, and every section (DO NOT, Workflow, Resources) earns its tokens, fitting the score-3 anchor.	3 / 3
Actionability	Provides executable commands (alembic revision --autogenerate -m, alembic upgrade head, alembic downgrade -1) and copy-paste-ready SQLAlchemy mappings (Long/19 -> BigInteger, ForeignKey("table.id"), op.bulk_insert), exceeding the score-2 pseudocode bar.	3 / 3
Workflow Clarity	An explicit 8-step sequence with validation checkpoints for a database operation — step 7 verifies apply + downgrade path, step 8 diffs schema column-by-column — providing the feedback loops the rubric requires to exceed 2.	3 / 3
Progressive Disclosure	No bundle files are needed; the body is organized into clearly delineated sections (Instructions, DO NOT, Workflow, Resources) with one-level-deep repo-doc references, satisfying the simple-skill allowance for a 3.	3 / 3
	Total	12 / 12 Passed

Description

100%

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

A precise, third-person description that states concrete capabilities and gives explicit, natural trigger phrases for both creating new migrations and making incremental schema changes. It cleanly satisfies the what-and-when requirements with minimal risk of overlapping other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'tables, columns, primary keys, foreign keys, unique and functional constraints ... reference-data seeds' — matching the score-3 anchor rather than the partial score-2 example.	3 / 3
Completeness	Explicitly answers both 'what' (creates versioned Alembic migration scripts...) and 'when' ('Use when the user asks to ...'), with third-person voice and no missing-trigger gap that would cap it at 2.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would actually say ('create a migration', 'add a column', 'add a foreign key', 'seed reference data') plus 'Alembic, schema migration, database schema changes'; well above the score-2 'some keywords' bar.	3 / 3
Distinctiveness Conflict Risk	A clearly defined Alembic-migration niche with distinct triggers unlikely to fire for unrelated skills; far more specific than the score-2 'Works with document files' overlap case.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: adolfobolivar/VETOnline
Commit: dee4c03

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