db-migration

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

Quality

85%

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

85%Weight 40%Scale 1-3

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 a clear sequenced workflow, validation, and error-recovery guidance. The main improvement opportunity is reducing repetition of the safety constraints (env flag, never-edit-manually) across multiple sections.

Suggestions

State each safety constraint once in its canonical location and reference it rather than repeating "--env local" and "never edit manually" across Context, steps, and Important Reminders.

Consider moving the Mixins table and Field/Edge/Index Patterns into a references file if the SKILL.md grows further, keeping the body as a tighter workflow overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence (no basic-concept padding), but "--env local" and the "never edit manually" prohibitions are repeated across Context, individual steps, and Important Reminders, so it could be tightened rather than restated.	2 / 3
Actionability	It provides fully executable commands ("make generate", "atlas migrate --env local diff <migration-name>", "atlas migrate --env local hash"), concrete file paths, and real Go mixin code, matching the copy-paste-ready level-3 anchor.	3 / 3
Workflow Clarity	The five steps are clearly sequenced with validation checkpoints ("Check that it completes without errors", review the generated migration) and feedback loops (fix schema then re-run make generate; rehash atlas.sum), satisfying the database-operation feedback-loop requirement so it is not capped at 2.	3 / 3
Progressive Disclosure	It is a single self-contained file with well-organized sections (Context, Workflow, Mixins, Patterns, Troubleshooting, Reminders) and no nested or deep references; the inline reference material (mixins table, field patterns) is compact and directly used in the workflow.	3 / 3
	Total	11 / 12 Passed

Description

85%Weight 40%Scale 1-3

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 pairs concrete capabilities with an explicit "Use when" trigger. Its only weakness is the reliance on the jargon term "ent schema" in the trigger, which slightly limits natural-keyword coverage.

Suggestions

Add more user-natural trigger phrasing alongside the jargon, e.g. "Use when adding or changing database fields/tables, modifying the ent schema, or generating migration files" so users who don't say "ent schema" still match.

Dimension	Reasoning	Score
Specificity	"Create or update database schema and generate migrations" names multiple concrete actions (create, update, generate), matching the level-3 anchor of listing several specific actions rather than the vague level-1/2 examples.	3 / 3
Completeness	It explicitly states both what it does ("Create or update database schema and generate migrations") and when to use it ("Use when modifying ent schema, adding database fields/tables, or generating migration files"), matching the level-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	"adding database fields/tables" and "generating migration files" are natural terms, but "ent schema" is framework-specific jargon a user would not naturally say, so it does not reach the full coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The ent-schema and migration-generation niche with codebase-specific triggers ("ent schema", "migration files") is clearly distinct and unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 12 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: 5936703

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