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.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

A highly actionable, well-sequenced migration skill with strong validation feedback loops for destructive database operations. Its main weakness is token redundancy from repeating setup commands across standalone sections and a lack of progressive file split for the longer help/pitfalls content.

Suggestions

Factor the repeated `cd backend` / `alembic current` setup into a single shared preamble or note ('All commands run from backend/') instead of restating it in every section to save tokens.

Move the full command help block (Section 7) and the Common Pitfalls list into a referenced file (e.g. references/REFERENCE.md) to deepen progressive disclosure and shorten SKILL.md.

Consider extracting the detailed autogenerate review checklist (Step 4) into a references file, keeping SKILL.md focused on the workflow sequence.

Dimension	Reasoning	Score
Conciseness	Mostly lean command-driven guidance with genuinely useful domain pitfalls, but `cd backend` and `alembic current` are repeated across the seven standalone command sections and the help block restates commands, leaving minor trimmable redundancy.	4 / 5
Actionability	Fully executable, copy-paste-ready Alembic commands (e.g. `alembic revision --autogenerate -m`, `alembic upgrade head`, `alembic downgrade -1`) cover all common cases across create, review, upgrade, downgrade, status, and history.	5 / 5
Workflow Clarity	The create flow sequences verify-DB → check model changes → generate → review ('critical!') → test (upgrade, verify, downgrade, re-apply), providing explicit validation checkpoints and a fix/retry feedback loop for this destructive database skill.	5 / 5
Progressive Disclosure	Well-organized numbered sections with clear navigation and no nested references, but ~190 lines are entirely inline with no one-level-deep external references, and the help text and pitfalls could justify splitting into separate files.	4 / 5
	Total	18 / 20 Passed

Description

100%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, third-person description that concretely names the migration lifecycle actions and pairs them with explicit, natural-language trigger guidance. It is comprehensive yet concise with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists four concrete lifecycle actions ('Create, review, test, and rollback Alembic database migrations') giving comprehensive coverage of the migration domain rather than minor gaps.	5 / 5
Completeness	Explicitly states what the skill does (create/review/test/rollback migrations) and when to use it via concrete 'Use this skill whenever...' and 'Also use when...' trigger clauses.	5 / 5
Trigger Term Quality	Covers natural terms and synonyms users would say — 'database migrations, alembic, schema changes, adding/modifying columns or tables, model changes' and the quoted phrase 'migrate the database' — comprehensively.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Alembic migrations for OPRE OPS — with distinct, domain-specific triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	20 / 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: 567e1df

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