db-migration

Create or update database schema and generate migrations. Use when modifying ent schema, adding database fields/tables, or generating migration files.

Quality

83%

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

82%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 well-structured, highly actionable migration skill with concrete commands, a clear workflow, and useful reference material. Its main weakness is that destructive/batch migration work lacks an explicit validation gate in the core workflow.

Suggestions

Add an explicit validation checkpoint in the workflow (e.g., after Step 5, run the view parity test or a dry-run migrate before presenting the summary) since migrations are destructive/batch operations.

Consolidate the repeated 'DO NOT edit manually / never edit migration files manually' reminders into one clearly marked section to trim redundant tokens.

Consider moving the Mixin reference table into a separate references file and linking to it, leaving SKILL.md as a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and skippable, assuming Claude knows ent/Atlas basics, with only minor over-explanation such as restating that generated code and migrations should not be hand-edited multiple times.	4 / 5
Actionability	It gives exact, copy-paste-ready commands ('make generate', 'atlas migrate --env local diff <migration-name>'), real file paths, and a concrete Mixin reference table covering the common cases.	5 / 5
Workflow Clarity	A clearly numbered five-step sequence with a review/verify checkpoint in Step 5 and a troubleshooting feedback loop, but for destructive database migration operations there is no explicit validate-before-proceed gate capping it below 5.	4 / 5
Progressive Disclosure	Well-organized sections with inline reference tables and real path pointers ('openmeter/ent/schema/*.go', 'tools/migrate/view_parity_test.go') rather than nested external references; no bundle files exist, so structure is self-contained with minor gaps.	4 / 5
	Total	17 / 20 Passed

Description

83%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 clearly states both capability and trigger conditions with concrete, domain-specific language. It would benefit from a few additional synonyms to round out trigger coverage.

Suggestions

Add natural synonyms and file extensions to the trigger clause (e.g., 'altering tables', '.sql migrations', 'database schema changes') to broaden trigger-term coverage.

Consider naming the migration format (golang-migrate) in the description to further sharpen distinctiveness from other DB skills.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions ('Create or update database schema and generate migrations') with only minor coverage gaps such as omitting rollback/down-migration generation.	4 / 5
Completeness	It explicitly answers both 'what' ('Create or update database schema and generate migrations') and 'when' ('Use when modifying ent schema, adding database fields/tables, or generating migration files') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases like 'modifying ent schema', 'adding database fields/tables', and 'generating migration files', though it lacks synonyms like 'alter table' or the explicit file extension '.sql'.	4 / 5
Distinctiveness Conflict Risk	The 'ent schema' framing carves a clear niche that other skills are unlikely to claim, but the broader database/migration scope carries minor overlap risk with general DB tooling skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: openmeterio/openmeter
Path: .agents/skills/db-migration/SKILL.md
Commit: 03a90ec

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.