CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

net8-security-auth-manager

Ativado ao configurar a autenticação e autorização (JWT Bearer, Roles e Políticas de Acesso) nas fatias verticais da camada de API do .NET 8.

Quality

63%

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-security-auth-manager/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.

The skill body is well-organized and reasonably lean, giving solid architectural direction (JWT config, role attributes, IUserContext abstraction, seeding). Its main weaknesses are placeholder code skeletons where executable examples are needed, no validation steps to confirm the security setup works, and a broken machine-specific file:// reference.

Suggestions

Complete the placeholder snippets: fill in the AddJwtBearer TokenValidationParameters (ValidIssuer, ValidAudience, IssuerSigningKey, expiry) and the actual claim-reading implementation of UserContext so the guidance is copy-paste executable.

Add validation checkpoints, e.g. confirm an unauthenticated request to a protected endpoint returns 401, a wrong-role request returns 403, and the seeded admin can log in.

Replace the absolute file:///mnt/c/... link to secret-management.md with a bundle-relative path (or inline the essential guidance), and verify the referenced AGENTS.md actually exists in the bundle.

DimensionReasoningScore

Conciseness

The body is largely efficient — short code snippets, terse bullet directives like "Registre o serviço na DI: `builder.Services.AddScoped<IUserContext, UserContext>();`" — with only minor trimmable padding (the opening paragraph restates the frontmatter, and lead-ins like "Para garantir a identidade dos usuários..." add little). It sits between anchor 3 (some unnecessary explanation) and anchor 5 (every token earns its place), so 4.

4 / 5

Actionability

Guidance is a mix of concrete and placeholder: `builder.Services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)` and `[Authorize(Roles = "AgenteQualidade")]` are executable, but `.AddJwtBearer(options => { ... })` and the `UserContext` class (`// ... ler as claims ...`) are literal skeletons, and the actual TokenValidationParameters wiring is absent. This matches anchor 3 (some concrete guidance but incomplete; pseudocode instead of executable code; missing key details) rather than anchor 4's mostly-executable bar.

3 / 5

Workflow Clarity

Sections are numbered and ordered (token config, endpoint protection, roles/policies, IUserContext, seeding), but there is no validation checkpoint anywhere — nothing on verifying a protected endpoint returns 401/403, testing token expiry, or confirming the seeded admin user works. Anchor 3 (steps listed but validation gaps; checkpoints missing) fits; not 4 because no checkpoint is present at all, not 2 because the sequence is coherent and well-structured.

3 / 5

Progressive Disclosure

The single-file body (~68 lines) is organized into clear sections, but the only external references are broken or dangling: the link to secret-management.md uses a machine-specific absolute path (file:///mnt/c/Users/jose.dotta/...) rather than a bundle-relative path, and `AGENTS.md` is referenced without existing in the bundle. This is 'some structure; references present but not clearly signaled/usable' (anchor 3) rather than anchor 4's mostly-clear reference placement.

3 / 5

Total

13

/

20

Passed

Description

52%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 strong, explicit trigger clause with good domain-specific keywords, but it omits any statement of what the skill does, leaving the 'what' half of the equation unanswered. Adding a capability statement (e.g., 'Define padrões de configuração de JWT, Roles, Políticas e abstração de IUserContext...') would make it complete.

Suggestions

Add an explicit 'what' statement before the trigger clause, e.g. 'Orienta a implementação de autenticação JWT Bearer, autorização por Roles e Políticas, e abstração de contexto do usuário. Ativado ao configurar...'.

Include additional natural trigger synonyms such as 'token', 'login', 'segurança' and 'claims' to broaden keyword coverage.

State the concrete deliverables (configuração do JwtBearer, atributos [Authorize], interface IUserContext, seeding de Roles) to lift specificity beyond one generic 'configurar' action.

DimensionReasoningScore

Specificity

The description names the domain ("autenticação e autorização") and specific technologies ("JWT Bearer, Roles e Políticas de Acesso", ".NET 8", "fatias verticais da camada de API"), but the only action named is the generic "configurar" — one action, not a comprehensive list. It matches anchor 3 (names domain and 1-2 concrete actions, not comprehensive); it is above anchor 2 because the parenthetical technology list is concrete, and below anchor 4 which requires several distinct specific actions.

3 / 5

Completeness

"Ativado ao configurar..." provides an explicit 'when' (trigger) clause, but there is no statement of what the skill actually does — no verbs describing capabilities or outcomes. This matches anchor 2 ("only 'when' is present without 'what'"). The trigger clause does exist, so it is above anchor 1, but the absent 'what' prevents the 3-4 range.

2 / 5

Trigger Term Quality

Terms like "autenticação", "autorização", "JWT Bearer", "Roles", "Políticas de Acesso", ".NET 8" are natural phrases a user would say when needing this skill. It falls short of anchor 5's comprehensive synonym coverage (e.g., "token", "login", "segurança", "claims" are missing) but exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (JWT Bearer auth, Roles/Policies authorization in .NET 8 vertical-slice APIs) with distinct trigger terms, giving minimal conflict risk with unrelated skills. Minor overlap risk remains with other general .NET/ASP.NET configuration skills, so it is below anchor 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

JoseMD12/testing-tessl

Path

plugins/dotnet-clean-arch/skills/net8-security-auth-manager/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.