migrations

Implementation details for EF Core migrations. Use when changing MigrationsSqlGenerator, model diffing, migration operations, HistoryRepository, the Migrator or related classes.

Quality

82%

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

86%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, well-structured reference for EF Core migration internals that assumes Claude's competence and wastes no tokens. Sequences and test paths are concrete; the only gap is the absence of executable code blocks, which is acceptable for an instruction-only knowledge skill.

Dimension	Reasoning	Score
Conciseness	Extremely lean: every line is a specific class, method, or test path with zero padding and no explanation of concepts Claude already knows; each token earns its place.	5 / 5
Actionability	Concrete, specific guidance throughout (method chains like 'MigrationsScaffolder.ScaffoldMigration() -> MigrationsModelDiffer.GetDifferences()' and exact test paths), giving actionable navigation for an instruction-only knowledge skill, but there are no copy-paste-ready code blocks.	4 / 5
Workflow Clarity	Both the 'Add migration' and 'Apply migration' pipelines are clearly sequenced with explicit -> arrows showing the code flow; these are descriptive internal-pipeline references rather than operational destructive workflows, so the validation cap does not squarely apply, though no checkpoints are present.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references; content is cleanly organized into Pipeline, Model Snapshot, and Testing sections, satisfying the simple-skill exception for a 5.	5 / 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 well-targeted, third-person description that names specific EF Core migration classes and gives an explicit 'Use when' trigger. It is distinct and trigger-rich, held back only by a slightly generic 'what' clause and a broad 'or related classes' tail.

Dimension	Reasoning	Score
Specificity	Names several concrete components ('MigrationsSqlGenerator', 'model diffing', 'migration operations', 'HistoryRepository', 'the Migrator'), giving specific targets rather than vague language, but the 'or related classes' catch-all leaves minor coverage gaps rather than a comprehensive action list.	4 / 5
Completeness	Provides both a 'what' ('Implementation details for EF Core migrations') and an explicit 'when' ('Use when changing ...'), with concrete trigger phrases; the 'what' is slightly generic ('implementation details'), keeping it just below a 5.	4 / 5
Trigger Term Quality	Includes natural trigger phrases an EF Core contributor would actually say ('EF Core migrations', 'MigrationsSqlGenerator', 'model diffing', 'HistoryRepository'), but lacks synonyms or file extensions and leans on technical jargon, stopping short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow, well-defined niche (EF Core migrations internals with specific named classes), making it clearly distinguishable with minimal conflict risk against other skills.	5 / 5
	Total	17 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: dotnet/efcore
Path: .agents/skills/migrations/SKILL.md
Commit: 3772265

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