This skill is an empty placeholder with no actual content. It contains only a title and a TODO comment, providing zero guidance on database migration creation or management. It fails every dimension of the rubric as there is nothing to evaluate beyond the absence of content.

Suggestions

Add concrete, executable examples of creating migrations (e.g., specific CLI commands for the target migration framework like `alembic revision --autogenerate -m 'add users table'`).

Define a clear multi-step workflow with validation checkpoints: create migration → review generated SQL → test migration up/down → verify schema state.

Include specific guidance on common migration patterns (adding columns, renaming, data migrations) with copy-paste ready code examples.

Add safety constraints and rollback procedures, especially for destructive operations like dropping columns or tables.

Dimension	Reasoning	Score
Conciseness	The content is essentially empty — a TODO placeholder with no actual instructions. While it's not verbose, it provides zero useful content, which is the worst outcome for token efficiency since even the tokens used (the title and TODO) add no value.	1 / 3
Actionability	There is no concrete guidance, no code, no commands, and no examples. The skill is entirely a placeholder with no actionable content whatsoever.	1 / 3
Workflow Clarity	Database migrations are inherently multi-step processes requiring validation checkpoints, yet no steps, sequences, or validation are provided — just a TODO stub.	1 / 3
Progressive Disclosure	There is no structure, no references, no organization — just a heading and a TODO line. No bundle files exist to support the content either.	1 / 3
	Total	4 / 12 Passed

Description

22%

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 description is too terse and vague to effectively guide skill selection. It uses second-person voice ('you need to'), lacks specific concrete actions, and provides no explicit trigger terms or 'Use when' clause with natural keywords. The domain of 'database migrations' is somewhat distinctive but the description needs significantly more detail about what it actually does.

Suggestions

Add specific concrete actions like 'Generate migration files, apply schema changes, rollback migrations, track migration history' to replace the vague 'create and manage'.

Add an explicit 'Use when...' clause with natural trigger terms such as 'schema changes', 'migrate database', 'migration files', 'db migrate', 'table alterations', and any specific frameworks supported.

Rewrite in third person voice (e.g., 'Creates and manages database migrations...' instead of 'When you need to create...').

Dimension	Reasoning	Score
Specificity	The description mentions 'create and manage database migrations' but does not list any concrete actions beyond these two vague verbs. It lacks specifics like 'generate migration files', 'run up/down migrations', 'track schema changes', etc.	1 / 3
Completeness	The 'what' is very weak (just 'create and manage') and while it starts with 'When you need to', this is second-person voice and the guidance is essentially just restating the vague capability rather than providing explicit trigger conditions. The description also uses second person ('you need to') which violates voice guidelines.	1 / 3
Trigger Term Quality	It includes 'database migrations' which is a relevant keyword users might say, but misses common variations like 'schema changes', 'migrate', 'migration files', 'db migrate', specific ORMs like 'Alembic', 'Knex', 'ActiveRecord', or file types.	2 / 3
Distinctiveness Conflict Risk	'Database migrations' is a reasonably specific domain that wouldn't overlap with most other skills, but the vagueness of 'create and manage' could cause overlap with general database management or ORM-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

12 days ago

Table of Contents

Discovery Implementation Validation