CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

net8-vertical-slice-generator

Ativado ao criar uma nova funcionalidade seguindo a arquitetura de fatias verticais (Vertical Slices) nas camadas API e Application do .NET 8.

Quality

60%

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-vertical-slice-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body is an efficient, well-scoped set of directives that correctly avoids teaching known concepts, but it stops short of being copy-paste actionable: class signatures are placeholders and there is no step-by-step creation sequence or full worked example. Promoting the placeholders to a complete example slice and adding a brief ordered workflow with a verification step would lift actionability and workflow clarity.

Suggestions

Replace the placeholder signatures with one complete executable example — a full Command, Validator, Handler, and Minimal API endpoint mapping for a sample feature.

Convert the diretrizes into an ordered creation workflow (create folder → add Command/Validator/Handler → map endpoint → verify it builds/returns expected status codes) with an explicit verification step.

Delete or shrink the intro paragraph that duplicates the frontmatter description, freeing tokens for the worked example.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanations of concepts Claude already knows; the only trimmable padding is the intro paragraph, which restates the frontmatter description almost verbatim ('orienta a criação e o scaffolding de novas funcionalidades... fatias verticais... nas camadas de API e Application do .NET 8').

4 / 5

Actionability

Concrete guidance exists — folder layout ('Application/Features/Chamados/AbrirChamado/'), class shapes ('public record Command(...) : IRequest<Result>;'), and error semantics ('400 Bad Request', '422 Unprocessable Entity') — but the signatures use '(...)' and '{ ... }' placeholders (pseudocode rather than executable code) and there is no complete example or command.

3 / 5

Workflow Clarity

The six numbered diretrizes give a rough implementation order (structure → API → validation → error handling → classes → business rules), but they read as a rule checklist rather than a sequenced creation workflow, and no validation or verification checkpoints are included.

3 / 5

Progressive Disclosure

As a compact (~26-line) single-file skill with no external references needed, inlining is appropriate and the numbered bold-labeled directives are well organized; minor gaps: a single section header and the example class signatures would be clearer as a fenced code block.

4 / 5

Total

14

/

20

Passed

Description

40%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 has a well-defined niche and decent trigger terms, but it only states when the skill activates — never what it does (e.g., scaffolds feature folders with Command/Validator/Handler and endpoint mapping). Adding an explicit capability statement with concrete trigger synonyms would raise both specificity and completeness.

Suggestions

Add a 'what' clause stating the concrete actions, e.g., 'Gera a estrutura de pastas da feature (Command/Query, Validator, Handler) com o endpoint da API... Ativado ao criar...'

Include more natural trigger variations users would say: 'feature', 'caso de uso', 'scaffold', 'endpoint', 'MediatR', 'nova funcionalidade .NET'.

Lead with capabilities in third person ('Gera... Scaffolda...') rather than only the activation condition, so both what and when are explicit.

DimensionReasoningScore

Specificity

The description names the domain precisely ('arquitetura de fatias verticais (Vertical Slices) nas camadas API e Application do .NET 8') but the only action stated is the generic 'criar uma nova funcionalidade' — no concrete capabilities (scaffold, generate handlers, map endpoints, validate) are listed.

2 / 5

Completeness

Only the 'when' is present ('Ativado ao criar uma nova funcionalidade...'); the 'what' — what the skill actually does when triggered — is entirely absent. This matches the anchor of only-'when'-without-'what' rather than the clear-what anchor at 3.

2 / 5

Trigger Term Quality

It includes relevant natural keywords with PT/EN synonyms ('criar', 'nova funcionalidade', 'fatias verticais (Vertical Slices)', '.NET 8'), but misses common variations users would say such as 'feature', 'use case', 'scaffold', 'endpoint', or 'MediatR'.

3 / 5

Distinctiveness Conflict Risk

The vertical-slice architecture pattern scoped to .NET 8 API/Application layers is a clear niche with distinct triggers, with only minor overlap risk against general .NET feature-creation skills.

4 / 5

Total

11

/

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-vertical-slice-generator/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.