CtrlK
BlogDocsLog inGet started
Tessl Logo

migrations

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

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, expert-level reference that packs internal EF Core migration architecture, a concrete gotcha, and exact test locations into a few well-organized sections with no padding. It exemplifies token-efficient, actionable knowledge content.

DimensionReasoningScore

Conciseness

The body is dense with real class names, method call chains, and file paths with no fluff or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It provides concrete, usable pointers — exact method chains (ScaffoldMigration() → GetDifferences() → ...), precise test paths, and a concrete gotcha about ClrType — which is actionable guidance for an instruction/knowledge skill even without runnable code.

3 / 3

Workflow Clarity

The pipeline is shown as a clearly sequenced → chain for both add and apply paths, and as a compact single-purpose skill under 50 lines the well-organized sections satisfy the simple-skill allowance.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized Pipeline / Model Snapshot / Testing sections meet the simple-skill criterion for a top score without bundle files.

3 / 3

Total

12

/

12

Passed

Description

100%

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 tight, specific description that names concrete EF Core migration components and includes an explicit 'Use when' trigger. It cleanly answers what the skill covers and when to invoke it with minimal risk of conflict.

DimensionReasoningScore

Specificity

The description lists multiple concrete named components — "MigrationsSqlGenerator, model diffing, migration operations, HistoryRepository, the Migrator" — rather than vague language, matching the anchor for listing several specific concrete items.

3 / 3

Completeness

It states what the skill covers ("Implementation details for EF Core migrations") and an explicit "Use when changing..." trigger clause, clearly answering both what and when.

3 / 3

Trigger Term Quality

Terms like "EF Core migrations", "MigrationsSqlGenerator", "HistoryRepository", and "the Migrator" are exactly the names an EF Core contributor would naturally invoke when working in this area, giving good domain coverage.

3 / 3

Distinctiveness Conflict Risk

The named internal classes and narrow EF Core migrations niche make it clearly distinguishable and very unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/efcore
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.