db-migrations

Create, review, test, rebase, and rollback Alembic database migrations for OPRE OPS. Use this skill whenever the user mentions database migrations, alembic, schema changes, adding/modifying columns or tables, model changes that need migration, "migrate the database", or a migration chain conflict / divergent heads after main has moved forward. Also use when a model change has been made and the user needs to generate the corresponding migration.

1.25x

Quality

88%

Does it follow best practices?

Impact

84%

1.25x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

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

An action-dense, well-sequenced operational skill: every workflow is executable with copy-paste commands and genuine validation loops, including the tricky rebase and stale-image cases. Its main weakness is structural — everything lives in one long file when the rebase procedure and reference material clearly belong in separate, clearly signaled reference files.

Suggestions

Split the detailed rebase procedure (Steps 1–5 with its chain-following and stale-image caveats) into a references/rebase.md file, keeping a short trigger summary in SKILL.md that links to it.

Move the default help text, Key File Locations, and Common Pitfalls into a references/reference.md so the main body stays a lean overview of the eight actions.

Tighten the rebase Step 2 and Step 5 prose — long multi-clause sentences explaining the stale-image false failure could be reduced to a short bulleted warning.

Dimension	Reasoning	Score
Conciseness	The body is command-first with almost no padding — no primer on what Alembic or migrations are, and the caveats (rename detection limits, NOT NULL backfill, stale data-import images) are genuinely non-obvious project knowledge rather than concepts Claude already knows. A few passages could still be tightened: the rebase Step 2/Step 5 prose uses dense multi-clause sentences, and the default help block repeats the section headers almost verbatim.	4 / 5
Actionability	Every action opens with copy-paste-ready bash (docker compose ps, alembic current, git diff, git show origin/main:...), placeholders are explicit (`<new-file>.py`, `<target>`, `<old-parent-revision>`), and file locations and naming patterns are spelled out, fully covering the common cases.	5 / 5
Workflow Clarity	Multi-step processes are explicitly sequenced (numbered Steps 1–5 for create and rebase) with real validation checkpoints throughout: verify the DB is running before generating, review the autogenerate output, test the downgrade round-trip, confirm one head after rebasing, and the explicit rebuild-before-verify loop for stale Docker images. Destructive operations (downgrade, down) all have verification steps, so the database-operations cap does not apply.	5 / 5
Progressive Disclosure	The file is well-sectioned with clear headers, but it is a ~246-line single file with no bundle structure at all — the rebase deep-dive (multi-file chain-following, stale-image caveats) and the help text are detail-heavy content that would sit better in one-level-deep reference files. This fits the anchor where content that should be separate is inline despite decent structure.	3 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 strong description in third person that states what it does with concrete verbs, gives explicit and varied use-when triggers, and is tightly scoped to Alembic/OPRE OPS so it is unlikely to fire for the wrong skill. The only gap is a handful of missing natural synonyms users might phrase differently.

Dimension	Reasoning	Score
Specificity	The description lists five concrete, distinct actions — "Create, review, test, rebase, and rollback Alembic database migrations" — anchored to a named tool and project (Alembic, OPRE OPS), which is comprehensive coverage with no vague filler.	5 / 5
Completeness	It explicitly answers both questions: the first sentence states what the skill does, and "Use this skill whenever the user mentions..." plus "Also use when a model change has been made and the user needs to generate the corresponding migration" give concrete when-triggers, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Strong natural coverage: "database migrations, alembic, schema changes, adding/modifying columns or tables, model changes that need migration, 'migrate the database', or a migration chain conflict / divergent heads". A few natural variants users might say (e.g. 'db migration', 'migration version', 'downgrade the database') are missing, so it falls just short of the comprehensive-with-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	"Alembic database migrations for OPRE OPS" carves out a clear niche with tool- and project-specific triggers (e.g. 'migration chain conflict / divergent heads after main has moved forward') that virtually no other skill would claim; conflict risk is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Repository: HHS/OPRE-OPS
Path: .claude/skills/db-migrations/SKILL.md
Commit: b61c72b

Reviewed: 19 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.