CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

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

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

A strong, focused body that encodes genuine project conventions (isolated Fluent API configurations, value object mapping strategy, strict migration naming, controlled migration flow) with concrete commands and API calls. The only notable weaknesses are a few sentences that over-explain known EF Core behavior and the absence of a recovery loop after migration review.

DimensionReasoningScore

Conciseness

The body is mostly lean, prescriptive rules encoding project-specific conventions Claude would not know (migration naming pattern 'v<numero_da_migration>_<nome_da_entidade_ou_agregador>_<acao_resumida>', backing-field policy, EnableRetryOnFailure). A few sentences explain EF Core behavior Claude already knows ('o EF Core é capaz de ler e escrever diretamente nos campos ou propriedades de apoio automaticamente') and could be trimmed, so it sits at anchor 4 rather than 5.

4 / 5

Actionability

Concrete API surface is named throughout (IEntityTypeConfiguration, ApplyConfigurationsFromAssembly, HasConversion, OwnsOne/OwnsMany, HasKey/HasIndex, EnableRetryOnFailure, context.Database.Migrate()) and the CLI command is copy-paste ready with real project paths ('dotnet ef migrations add v1_usuario_criar --project src/MachineReturn.Infra --startup-project src/MachineReturn.API'). The configuration class example is only a signature with '{ ... }' rather than executable body code, keeping it at anchor 4 instead of 5.

4 / 5

Workflow Clarity

The migration workflow is a clearly numbered sequence with explicit checkpoints: build must succeed before generating, the generated migration class and snapshot must be inspected (watching for empty operations and DropColumn/DropTable), and startup gets exception handling with retries. Validation steps are present, so the missing-validation cap at 3 does not apply; the remaining gap is that no recovery action is given when the migration review finds a problem (e.g., no 'dotnet ef migrations remove' guidance), which matches anchor 4's 'minor validation gaps' rather than anchor 5's explicit fix-and-retry feedback loops.

4 / 5

Progressive Disclosure

A single ~55-line SKILL.md with two well-organized sections (Mapeamento de Entidades, Migrações do EF Core) and no bundle files; there is no content that needs splitting into references and no nested navigation, so under the simple-skill guidance well-organized sections alone justify a 5.

5 / 5

Total

17

/

20

Passed

Description

61%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 distinctive, well-targeted trigger description with concrete actions and natural keywords, but it is missing the 'what': it says when the skill activates without ever stating what the skill does or enforces. Adding a one-clause capability statement before the trigger would lift it substantially.

Suggestions

Add a 'what' clause stating what the skill does, e.g. 'Enforces isolated Fluent API entity configurations, value object mapping, and a controlled EF Core migration workflow (naming, review, resilient application).' before the trigger clause.

Include natural trigger variations users might say, such as 'Fluent API', 'OnModelCreating', or 'dotnet ef migrations add', alongside the existing 'DbContext' and 'EF Core Migrations' terms.

DimensionReasoningScore

Specificity

The description lists several specific actions — 'configurar classes de entidade no DbContext (Entity Configuration)', 'criar e aplicar migrações (EF Core Migrations)' — anchored to a concrete stack (.NET 8 Infrastructure layer). It stays at anchor 4 rather than 5 because coverage has minor gaps (value object mapping, migration naming governance, resiliency conventions from the body are not reflected).

4 / 5

Completeness

The entire description is a single trigger clause ('Ativado ao...' = 'Activated when...'): the 'when' is specific, but the 'what' — what the skill actually does (enforce isolated Fluent API configurations, value object mapping rules, and a controlled migration workflow) — is never stated. This matches anchor 2's 'only when is present without what'; it cannot be 3 because there is no clear 'what' and the implied capabilities do not surface what the skill enforces.

2 / 5

Trigger Term Quality

Good natural keyword coverage: 'DbContext', 'Entity Configuration', 'EF Core Migrations', 'migrações', '.NET 8', 'camada de Infraestrutura' are phrases a user working in this codebase would actually say. Not anchor 5 because common variations such as 'Fluent API', 'OnModelCreating', or 'dotnet ef' are missing.

4 / 5

Distinctiveness Conflict Risk

EF Core entity configuration and migrations in the .NET 8 Infrastructure layer is a clear niche with distinct, unambiguous triggers; there is minimal overlap risk with any neighboring skill. Fits anchor 5 cleanly.

5 / 5

Total

15

/

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

JoseMD12/testing-tessl

Path

plugins/dotnet-clean-arch/skills/efcore-config-migration-enforcer/SKILL.md

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.