create-migration

Create and apply an EF Core migration for a module's DbContext the FSH way (central Migrations project, per-module folder, correct --context). Use after changing entities/EF config. See .agents/rules/database.md.

Quality

84%

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

90%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 tight, highly actionable migration runbook with executable commands, a real validation step, and a checklist — well-matched to a destructive database operation. The only meaningful gap is that the fix-and-retry feedback loop after SQL review is implied rather than explicit.

Dimension	Reasoning	Score
Conciseness	Lean throughout: no preamble explaining what EF Core or migrations are, and every line earns its place — the Step 1 'snapshot footgun' warning and the BaseDbContext edge-case note are non-obvious knowledge Claude would not already have. Matches anchor 5's 'every token earns its place'.	5 / 5
Actionability	Every step is a copy-paste-ready command with all required flags spelled out ('dotnet ef migrations add {MigrationName} --project ... --startup-project ... --context {X}DbContext --output-dir {X}'); placeholders are necessary parameterization, not pseudocode, matching anchor 5.	5 / 5
Workflow Clarity	Clear Step 0–4 sequence with an explicit validation step (Step 3 reviews generated SQL for data loss) and a closing checklist, so it clears the destructive-operation cap; held at 4 rather than 5 because the feedback loop is only implied ('Adjust the model or hand-edit the migration if needed') without an explicit re-validate/re-review step.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Steps 0–4, Notes, Checklist) with one-level-deep, clearly signaled external pointers ('see .agents/rules/database.md', 'see add-module'); no bundle files exist and all content is core workflow that belongs inline, but it is slightly over the ~50-line simple-skill threshold, so it sits at 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

78%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 specific, third-person description that clearly states both the capability and a concrete use trigger, with strong distinctiveness. It could rise to top marks by adding a few more natural trigger synonyms (e.g., 'database update', '.NET migration') and broadening the 'when' clause.

Suggestions

Add 1-2 natural trigger synonyms (e.g., 'database update', '.NET data migration') to broaden trigger_term_quality and completeness toward a 5.

Expand the 'Use after...' clause with an additional concrete trigger (e.g., 'or when adding a new module DbContext') to reach the multi-trigger anchor 5 for completeness.

Consider listing a third concrete action (e.g., 'review generated SQL') to push specificity from 4 to 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('EF Core migration for a module's DbContext') and concrete actions ('Create and apply') plus specific mechanics in the parenthetical ('central Migrations project, per-module folder, correct --context'); falls just short of anchor 5's 'comprehensive coverage' since only two verbs carry the action list.	4 / 5
Completeness	Explicitly answers both what ('Create and apply an EF Core migration...') and when ('Use after changing entities/EF config'); the 'when' is a single concrete trigger rather than the multiple trigger phrases of anchor 5, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	Covers natural terms a user would say ('EF Core migration', 'DbContext', 'entities', 'EF config') with a clear trigger ('Use after changing entities/EF config'); missing common synonyms/variations like 'database update' or '.NET migration', so not a 5.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche ('EF Core migration... the FSH way', central Migrations project, per-module context) that is unlikely to fire for unrelated skills; minimal conflict risk matching anchor 5.	5 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fullstackhero/dotnet-starter-kit
Path: .agents/skills/create-migration/SKILL.md
Commit: 3f2959e

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