db-migrations

Create, review, test, 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, or "migrate the database". Also use when a model change has been made and the user needs to generate the corresponding migration.

0.98x

Quality

—

Does it follow best practices?

Impact

96%

0.98x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is highly actionable and well-sequenced with strong validation feedback loops for a risky database workflow, and it avoids explaining concepts Claude already knows. The main weakness is progressive disclosure: everything lives in one long inline file with no references to offload detail.

Suggestions

Move the full command help block and/or the detailed Common Pitfalls catalog into a reference file (e.g. references/PITFALLS.md), keeping SKILL.md as a concise overview with a one-level-deep pointer.

Consider extracting the create-migration review checklist (Step 4) into a separate reference so the main workflow stays lean while the detailed correctness checks remain discoverable.

Trim repeated boilerplate such as repeated 'cd backend' lines and the restated Prerequisites section to further tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and task-oriented with no conceptual padding about what Alembic or migrations are; each token earns its place, though minor redundancies (repeated cd backend, restated prerequisites) keep it just within the lean anchor.	3 / 3
Actionability	Provides fully executable bash commands and exact file paths throughout (e.g. "alembic revision --autogenerate -m", "git diff main...HEAD --name-only -- models/", "ls -t backend/alembic/versions/*.py \| head -1"), copy-paste ready.	3 / 3
Workflow Clarity	The create flow is a clearly sequenced 5-step process with explicit validation checkpoints and a feedback loop (Step 4 review checklist, Step 5 upgrade→downgrade→re-apply test), appropriate for a destructive database operation.	3 / 3
Progressive Disclosure	Well organized with clear section headers, but the 191-line file is monolithic with the full help block and pitfall catalog inline; some of this could be offloaded to a reference file rather than kept in the overview.	2 / 3
	Total	11 / 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.

The description is strong: it names concrete actions, provides explicit 'Use when' trigger guidance with natural keyword coverage, and is scoped to a clear, distinctive niche. No significant weaknesses; no changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Create, review, test, and rollback Alembic database migrations") rather than vague language, matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what (create/review/test/rollback Alembic migrations) and when ("Use this skill whenever the user mentions... Also use when..."), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Covers natural phrasings users would say ("database migrations", "alembic", "schema changes", "adding/modifying columns or tables", "migrate the database"), giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to "Alembic database migrations for OPRE OPS" with migration-specific triggers, giving it a clear niche unlikely to conflict with unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: 908aa71

Reviewed: 5 days 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.