CtrlK
BlogDocsLog inGet started
Tessl Logo

model-building

Implementation details for EF Core model building. Use when changing ConventionSet, ModelBuilder, IConvention implementations, ModelRuntimeInitializer, RuntimeModel, or related classes.

76

Quality

95%

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 high-quality internal reference skill: lean, concrete, and well-organized, with explicit file paths, method names, sequenced procedures, and a verification checklist. It assumes reader competence and avoids concept padding entirely.

DimensionReasoningScore

Conciseness

The body is dense reference material that assumes C#/EF Core competence (e.g. 'ConventionSet ... holds List<I*Convention> for every metadata event') with no padding or explanations of basic concepts; every section earns its place.

3 / 3

Actionability

As an instruction-only codebase skill it provides concrete, actionable guidance — exact file paths (src/EFCore/Metadata/Conventions/), method signatures (ConfigureConventions(ModelConfigurationBuilder), GetFlattenedProperties()), and a 4-step annotation procedure — which the rubric rewards without requiring executable code blocks.

3 / 3

Workflow Clarity

Multi-step processes (Model Lifecycle, 'Adding a New Annotation') are clearly sequenced, and a dedicated 'Validation' checklist plus the snapshot round-trip test recommendation provide explicit verification and cause→fix error-recovery guidance for migration-risky changes.

3 / 3

Progressive Disclosure

It is a single cohesive reference file (~90 lines) organized into clearly headed sections (Convention System, Metadata Hierarchy, Model Lifecycle, Relational Model, Testing) with no nested references and no monolithic wall of text, appropriate for a self-contained overview.

3 / 3

Total

12

/

12

Passed

Description

90%

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 tightly scoped, well-constructed description with an explicit 'Use when' trigger and precise class-name keywords. The only weakness is that it describes the domain rather than enumerating concrete actions, capping specificity at 2.

DimensionReasoningScore

Specificity

The phrase 'Implementation details for EF Core model building' names the domain and trigger classes precisely, but does not list concrete capability actions (unlike 'extract text and tables, fill forms, merge documents'), so it sits at the 'names domain and some actions' anchor rather than the multi-action anchor.

2 / 3

Completeness

It states what it covers ('Implementation details for EF Core model building') and gives an explicit 'Use when changing...' trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

It lists the exact class names a developer would naturally say ('ConventionSet, ModelBuilder, IConvention implementations, ModelRuntimeInitializer, RuntimeModel'), giving strong coverage of the real trigger terms for this niche.

3 / 3

Distinctiveness Conflict Risk

The triggers are narrowly scoped to specific EF Core model-building internals, creating a clear niche unlikely to fire for unrelated skills; voice is third person with no first/second person penalty.

3 / 3

Total

11

/

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.