Conciseness

Quotes: "dotnet ef migrations add reads the current snapshot, which is regenerated from a build", "the canonical path — migrates the tenant catalog then each tenant's per-module schema". The body is lean: no explanation of what EF Core or migrations are, only project-specific facts Claude could not know (snapshot footgun, DbMigrator applying per-tenant schemas), so every token earns its place — anchor 5. It is not a 4 because there is no over-explanation that could be trimmed; the rationale lines are non-obvious project behavior, not padding.

Actionability

Quotes: "dotnet ef migrations add {MigrationName} --project src/Host/FSH.Starter.Migrations.PostgreSQL --startup-project src/Host/FSH.Starter.Api --context {X}DbContext --output-dir {X}", "dotnet run --project src/Host/FSH.Starter.DbMigrator -- apply", "dotnet tool restore". Every step is a fully executable command with real paths and flags; placeholders are clearly scoped ("match the existing folder for the context") and common cases are covered — anchor 5. It is not a 4 because there are no gaps: build, add, script, apply, and preview (list-pending) are all concrete.

Workflow Clarity

Quotes: "Step 1 — BUILD FIRST (snapshot footgun)", "Check for: unintended table/column drops, non-nullable columns added without a default..., and renames surfacing as drop+add (data loss). Adjust the model or hand-edit the migration if needed", "list-pending # to preview first", plus a closing Checklist. This is a clear 0→4 sequence with an explicit SQL-review validation checkpoint, a fix-and-retry loop ("adjust the model or hand-edit if needed"), and a checklist for a database operation — anchor 5. It is not a 4 because validation is explicit and error-recovery guidance is present, not merely implied; the destructive-operation cap does not apply since validation before applying is a first-class step.

Progressive Disclosure

Quotes: "All migrations live in one project... but are foldered per module/context", "see add-module", "see .agents/rules/database.md" (description). Sections (Steps, Notes, Checklist) are well organized and the body is self-contained with one-level-deep external pointers, matching anchor 4 (good structure, references mostly clear, minor organization gaps). It is not a 5 because at ~73 lines it exceeds the under-50-line simple-skill exception, and the pointers to add-module/.agents rules are terse rather than clearly signaled navigation; it is not a 3 because no content that belongs in a separate file is inlined and nothing is buried.

Specificity

Quotes: "Create and apply an EF Core migration for a module's DbContext", "central Migrations project, per-module folder, correct --context". It names the domain and concrete actions with specifics of how they must be done, but only covers two actions (create, apply) rather than a comprehensive list of capabilities, matching anchor 4. It is not a 3 ("1-2 concrete actions, but not comprehensive") because the parenthetical adds several concrete specifics (central project, per-module folder, correct --context); not a 5 because coverage is limited to the create/apply pair.

Completeness

Quotes: what — "Create and apply an EF Core migration for a module's DbContext the FSH way"; when — "Use after changing entities/EF config.". Both what and when are explicitly stated, and the when clause uses a concrete trigger phrase, matching anchor 5. It is not a 4 because the 'when' is already explicit and specific (post-entity/config change), not merely present-but-vague.

Trigger Term Quality

Quotes: "EF Core migration", "DbContext", "entities/EF config". These are natural phrases a developer would say when needing this skill ("add an EF Core migration", "after changing entities"), giving good keyword coverage. A few natural variations are missing ("database update", "schema change", "migrations script"), so it fits anchor 4 rather than anchor 5's comprehensive synonym/extension coverage; it clearly exceeds anchor 3 ("some relevant keywords but missing common variations").

Distinctiveness Conflict Risk

Quotes: "for a module's DbContext the FSH way (central Migrations project, per-module folder, correct --context)". This carves out a clear niche — EF Core migrations in this specific FSH project layout — with triggers unlikely to fire for unrelated skills, matching anchor 5 (clear niche, distinct triggers, minimal conflict risk). It is not a 4 because the parenthetical constraints leave essentially no overlap risk with generic migration or database skills.