CtrlK
BlogDocsLog inGet started
Tessl Logo

efcore-config-migration-enforcer

Ativado ao configurar classes de entidade no DbContext (Entity Configuration) ou criar e aplicar migrações (EF Core Migrations) na camada de Infraestrutura do .NET 8.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/dotnet-clean-arch/skills/efcore-config-migration-enforcer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is concrete and highly actionable with real EF Core commands and API examples, organized into a clear multi-step migration workflow with review checkpoints. Main gaps are a missing automated validate-retry feedback loop and minor conciseness/organization trim.

Suggestions

Add an explicit validation feedback loop for migrations (e.g., run 'dotnet ef migrations script --idempotent' or a build/EF validation step, fix, and only apply when it passes).

Tighten the explanatory rationale sentences (e.g., the container-startup justification) to leaner directive statements.

Consider moving the detailed entity-mapping recipes (value objects, keys/indexes) into a separate references file with a one-level-deep pointer from SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly lean, directive guidance with concrete API names and commands; only minor rationale prose (e.g., explaining container startup latency) could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: real CLI command ('dotnet ef migrations add v1_usuario_criar --project ... --startup-project ...') and specific API calls (ApplyConfigurationsFromAssembly, HasConversion, OwnsOne, HasKey, HasIndex, EnableRetryOnFailure, context.Database.Migrate()).

5 / 5

Workflow Clarity

A clear five-step migration sequence exists with checkpoints (compile before migrating, review generated migration for destructive DropColumn/DropTable), but it lacks an explicit automated validate->fix->retry->only-proceed feedback loop for destructive operations.

4 / 5

Progressive Disclosure

Well-organized into two top-level sections with numbered subsections and no nested references; the body is slightly over the ~50-line simple-skill threshold and could optionally split detailed configuration recipes into a reference file.

4 / 5

Total

17

/

20

Passed

Description

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

The description is third-person and provides an explicit activation trigger tied to concrete EF Core activities, giving it strong distinctiveness and completeness. Specificity and trigger-term coverage are good but could list more actions and synonyms.

Suggestions

Add 1-2 more concrete capabilities (e.g., mapping value objects, configuring keys/indexes, resilience policies) to lift specificity beyond 1-2 actions.

Include common synonyms such as 'Entity Framework' or 'EF' alongside 'EF Core' so natural phrasings match more reliably.

State the skill's purpose as a separate explicit 'what' clause (e.g., 'Enforces EF Core configuration and migration best practices...') rather than relying on the trigger alone.

DimensionReasoningScore

Specificity

Names the domain (DbContext, Entity Configuration, EF Core Migrations, .NET 8 Infra) with a couple of concrete actions (configure entity classes, create/apply migrations), but coverage is not comprehensive of the full skill scope (value objects, keys, resilience).

3 / 5

Completeness

Explicit trigger guidance ('Ativado ao...') answers 'when' clearly and the actions convey 'what'; both are present with the 'when' being specific, just short of a fully separate explicit capability statement.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms a .NET developer would say ('DbContext', 'Entity Configuration', 'migrações', 'EF Core Migrations', '.NET 8'), though a few synonyms like 'Entity Framework' or 'EF' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (EF Core Entity Configuration + Migrations in the .NET 8 Infrastructure layer) with distinct triggers and minimal overlap risk against unrelated skills.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JoseMD12/testing-tessl
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.