CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

net8-error-handling-enforcer

Ativado ao implementar o middleware de tratamento global de exceções, validações com FluentValidation e mapeamento de respostas semânticas usando RFC 7807 (Problem Details) no .NET 8.

Quality

69%

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/net8-error-handling-enforcer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 focused, well-structured guide that gives correct, version-current .NET 8 guidance (IExceptionHandler over hand-rolled middleware, AddProblemDetails, HttpValidationProblemDetails) and concrete registration lines. Its main gaps are the missing executable GlobalExceptionHandler implementation — the heart of the skill — known-content padding around the ProblemDetails fields, and no verification step for the resulting error responses.

Suggestions

Add a complete, copy-paste-ready GlobalExceptionHandler example implementing IExceptionHandler.TryHandleAsync, showing the conditional mapping of DomainException and ValidationException to ProblemDetails/HttpValidationProblemDetails — this is the skill's core artifact and is currently only described.

Trim the per-property explanations of ProblemDetails (Type/Title/Status/Detail/Instance) that Claude already knows, keeping only project-specific requirements such as which fields are mandatory in this codebase.

Add a short verification step (e.g., 'Confirme que uma DomainException lançada retorna 400/422 com o payload ProblemDetails') so the workflow ends with a checkpoint instead of the middleware registration.

DimensionReasoningScore

Conciseness

The body is mostly directive, but it spends lines explaining things Claude already knows: the five ProblemDetails properties with per-field descriptions ("Type: URI que identifica o tipo de erro...", "Title: Uma descrição curta e legível por humanos...") and a fluffy framing intro ("assegurando que o cliente receba respostas semânticas, estruturadas e consistentes com o padrão da indústria"). This matches anchor 3 — mostly efficient with some unnecessary explanation — rather than anchor 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete and copy-paste-ready where it counts for wiring: `builder.Services.AddExceptionHandler<GlobalExceptionHandler>();`, `builder.Services.AddProblemDetails();`, `app.UseExceptionHandler();`, plus named APIs (IExceptionHandler, TryHandleAsync, HttpValidationProblemDetails, ILogger). However the core deliverable — the GlobalExceptionHandler implementation — is only described ("Implemente o método TryHandleAsync mapeando de forma condicional..."), never shown as executable code, matching anchor 3's 'concrete guidance but incomplete / missing key details' rather than anchor 4.

3 / 5

Workflow Clarity

There is a recognizable sequence — define exception-to-response mappings (DomainException → 400/422, ValidationException → 400 with Errors dictionary), then implement the handler class, then register and activate it in Program.cs — but no explicit ordering statement and no verification checkpoint (e.g., confirming a thrown DomainException returns a ProblemDetails payload). This is anchor 3: steps present, validation/checkpoints missing; anchor 4 would require an explicit validate step such as testing the error response.

3 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ are absent), and no content that warrants external files. It is organized into two well-labeled sections (## Diretrizes de Resposta HTTP Semântica, ## Implementação do Middleware Global) with numbered sub-steps, which per the simple-skill scoring note earns a 5 on well-organized sections alone.

5 / 5

Total

14

/

20

Passed

Description

65%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 highly specific, low-conflict trigger description in Portuguese that clearly signals when to use the skill, but it never states what the skill does — capabilities are only implicit in the trigger list. Adding an explicit capability statement (e.g., 'Padroniza o tratamento de exceções em APIs .NET 8 retornando ProblemDetails...') plus a few common synonyms would raise completeness and trigger coverage.

Suggestions

Add an explicit 'what' statement before the trigger clause, e.g. 'Padroniza o tratamento global de exceções em APIs .NET 8, traduzindo DomainException e ValidationException em respostas RFC 7807 (ProblemDetails).' and keep the 'Ativado ao implementar...' sentence as the 'when'.

Include common synonyms users might say — 'error handling', 'global exception handler', 'IExceptionHandler', 'HttpValidationProblemDetails' — so the description matches both Portuguese and English phrasings.

Clarify the skill's scope boundary (API-layer error responses only) to further reduce overlap with general .NET coding skills.

DimensionReasoningScore

Specificity

The description names a concrete, specific domain — "middleware de tratamento global de exceções, validações com FluentValidation e mapeamento de respostas semânticas usando RFC 7807 (Problem Details) no .NET 8" — but it states no capabilities the skill performs; it is purely a trigger phrase with the 'what' only implied by the trigger list. This sits between anchor 2 (domain named, actions minimal) and anchor 3 (domain plus 1-2 concrete actions), and above anchor 2 because the domain terms are themselves precise and multi-part.

3 / 5

Completeness

It has an explicit and detailed 'when' ("Ativado ao implementar...") but no statement of what the skill does — the capabilities are only implied by the trigger list. This falls between anchor 2 (only 'when' present without 'what') and anchor 3 (clear 'what', missing 'when'); it scores 3 rather than 2 because the trigger clause is specific enough to convey the skill's scope, unlike the vague 'Use when working with documents' example.

3 / 5

Trigger Term Quality

Strong natural keywords a .NET developer would say: "middleware de tratamento global de exceções", "FluentValidation", "RFC 7807 (Problem Details)", "respostas semânticas", ".NET 8". Missing a few common variations such as "error handling", "IExceptionHandler", or "global exception handler", so it falls just short of the comprehensive-synonyms anchor 5.

4 / 5

Distinctiveness Conflict Risk

The combination of .NET 8, FluentValidation, RFC 7807 Problem Details, and global exception-handling middleware carves out a clear niche with distinct trigger terms; minimal risk of firing for an unrelated skill.

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/net8-error-handling-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.