CtrlK
BlogDocsLog inGet started
Tessl Logo

ef-migration

Generates Entity Framework Core (EF Core) database migrations for C# / .NET projects based on the entity model specification in docs/entity_model.md. Use when the user asks to "create database migration", "add ef migration", "update schema with ef core", "generate db migration for .net", or mentions EF Core, DbContext, or database migrations in C#.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

The body is concise and actionable with concrete EF Core commands and Fluent API patterns, and is well-structured for a simple skill. The main gap is workflow clarity: database migration is a schema-changing operation that lacks an explicit validation feedback loop.

Suggestions

Add an explicit validation feedback loop after generating the migration: e.g. 'If the migration class has unexpected operations, fix the entity/configuration and re-run dotnet ef migrations add' so destructive/schema operations have a clear validate->fix->retry path.

Clarify the step-4 verification into a concrete checkpoint command (e.g. 'dotnet ef migrations list' or a build step) so the verify action is executable rather than implied.

Optionally include one complete, copy-paste-ready IEntityTypeConfiguration<T> example to lift actionability from concrete snippets to fully executable coverage.

DimensionReasoningScore

Conciseness

Lean and mostly efficient: it does not explain concepts Claude already knows (no 'what is EF Core' padding) and uses tight numbered instructions; the copyright header and the quoted 'Next step' block are minor non-instructional padding that keeps it just below a 5.

4 / 5

Actionability

Provides concrete, mostly-executable guidance — specific command 'dotnet ef migrations add UCXXX_Description' with project flags, and concrete Fluent API snippets (HasPrecision(18, 2), HasConversion<string>(), IEntityTypeConfiguration<T>) — but stops short of a full copy-paste-ready example, matching the 4 anchor.

4 / 5

Workflow Clarity

Steps 1-6 give a clear sequence with one verify checkpoint ('Verify the generated migration class under Migrations/'), but migrations are schema-changing operations and there is no explicit validate->fix->retry feedback loop, so the destructive/batch feedback-loop cap of 3 applies.

3 / 5

Progressive Disclosure

A short (~26 line) single-purpose skill with clean Goal/Instructions sections and a clearly signaled one-level reference to docs/entity_model.md; no nested references and no bundle files to navigate, satisfying the simple-skill exception for a 5.

5 / 5

Total

16

/

20

Passed

Description

90%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 strong, well-structured description that clearly states both purpose and trigger conditions with natural user phrasings. The only modest dimension is specificity, which lists two concrete actions rather than a comprehensive set.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Generates Entity Framework Core (EF Core) database migrations' and 'configure entity models'), matching the 1-2 concrete actions anchor; not comprehensive enough for a 4.

3 / 5

Completeness

Explicitly answers both what ('Generates EF Core database migrations ... configure entity models') and when ('Use when the user asks to ...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrasings users would say ('create database migration', 'add ef migration', 'update schema with ef core', 'generate db migration for .net') plus technical synonyms (EF Core, DbContext) and language context (C#).

5 / 5

Distinctiveness Conflict Risk

Narrow niche (EF Core migrations for C#/.NET) with distinct, specific triggers; minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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
AI-Unified-Process/marketplace
Reviewed

Table of Contents

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.