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.
90
88%
Does it follow best practices?
Impact
96%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines concrete actions (create, review, test, rollback), specifies the tool and project context (Alembic, OPRE OPS), and provides comprehensive trigger guidance with natural user terms. It follows the recommended pattern of 'what it does' followed by 'Use when...' with multiple trigger scenarios, making it easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, review, test, and rollback Alembic database migrations for OPRE OPS.' These are distinct, actionable operations clearly scoped to a specific tool and project. | 3 / 3 |
Completeness | Clearly answers both 'what' (create, review, test, rollback Alembic migrations for OPRE OPS) and 'when' with an explicit 'Use this skill whenever...' clause listing multiple trigger scenarios including the reactive case of model changes needing corresponding migrations. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'database migrations', 'alembic', 'schema changes', 'adding/modifying columns or tables', 'model changes that need migration', 'migrate the database'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool (Alembic), project (OPRE OPS), and domain (database migrations). The trigger terms are narrowly scoped to database schema/migration work, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that provides clear executable commands and well-sequenced workflows for managing Alembic migrations in a specific project context. The create-migration workflow is particularly well done with explicit validation checkpoints and error recovery guidance. Minor improvements could be made in reducing some verbosity and better organizing the content to avoid duplication between the review checklist in the create flow and the standalone review section.
Suggestions
Deduplicate the review checklist by defining it once and referencing it from both the 'create' (Step 4) and 'review' sections, or extract it into a separate referenced file.
Trim the default help text section — Claude can generate help output dynamically rather than having it hardcoded in the skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and project-specific, but some sections could be tightened. The help text in the default section and some explanatory comments are slightly verbose. However, most content is project-specific knowledge Claude wouldn't have, which earns its place. | 2 / 3 |
Actionability | Every action includes fully executable bash commands with specific paths, flags, and expected patterns. The review checklist provides concrete items to verify. Commands are copy-paste ready and context-specific to the OPRE OPS project. | 3 / 3 |
Workflow Clarity | The 'create migration' workflow has a clear 5-step sequence with explicit validation checkpoints: verify DB is running, review generated migration (marked as critical), test upgrade/downgrade cycle, and report results. Error recovery is addressed (e.g., 'If the database isn't running, tell the user...'). The upgrade/downgrade/status flows all include verification steps. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical structure by command type. However, it's a single monolithic file with no references to external documentation. The review checklist in Step 4 is duplicated in Section 2, and the 'Common Pitfalls' and 'Key File Locations' sections could potentially be split out for a cleaner overview. For a skill of this length (~150 lines), some separation would improve scannability. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- HHS/OPRE-OPS
- Commit
e2a9461
- 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.