CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

52

Quality

57%

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 content is well-structured and mostly concise with concrete code examples, but truncated placeholder snippets reduce copy-paste actionability, no validation checkpoints are defined, and external references point to non-existent/non-portable files.

Suggestions

Replace truncated code placeholders (e.g., 'options => { ... }', 'policy => ...') with complete, executable snippets so the guidance is copy-paste ready.

Add explicit validation/verification checkpoints — e.g., after configuring JWT, verify a protected endpoint returns 401 unauthenticated then 200 with a valid token.

Fix the broken secret-management.md reference: convert the absolute file:/// path to a relative bundle path inside references/, or remove the link if the file is not bundled.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code blocks and direct guidance; only minor framing sentences ('Esta habilidade orienta...', 'Para garantir a identidade...') could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Provides concrete code (AddJwtBearer, the IUserContext interface, [Authorize], AddAuthorization, DI registration) but several snippets are deliberately truncated placeholders ('options => { ... }', 'policy => ...', '// ... ler as claims...'), which keeps it from copy-paste readiness.

3 / 5

Workflow Clarity

Sections are sequenced with numbered steps and concrete registration commands, but there are no explicit validation/verification checkpoints (the seeding step only implies verification), matching 'steps listed but validation gaps'.

3 / 5

Progressive Disclosure

Structure is clear with well-organized section headers, but the references to secret-management.md (via a non-portable absolute file:///mnt/c/... path) and AGENTS.md point to files absent from the bundle, so references are present but not clearly signaled or resolvable.

3 / 5

Total

13

/

20

Passed

Description

57%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 targets a specific, distinguishable niche but blends the 'what' and 'when' into a single trigger phrase, leaving the skill's concrete actions underspecified. It uses real keywords but lacks synonym coverage and a clear statement of capabilities.

Suggestions

Add a concrete 'what' clause listing the specific actions the skill performs (e.g., 'Registra autenticação JWT Bearer, configura autorização por Roles e Políticas, e abstrai o contexto do usuário via IUserContext') separate from the 'when' trigger.

Include natural-language synonyms/variations users might say (e.g., 'token', 'login', 'controle de acesso', 'permissões') alongside the technical jargon.

Keep the 'Use when.../Ativado ao...' trigger but pair it with an explicit capability statement so both 'what' and 'when' are answered distinctly.

DimensionReasoningScore

Specificity

Names the concrete domain (.NET 8 API auth/authz) and three concrete mechanisms (JWT Bearer, Roles, Políticas de Acesso), but these are config targets rather than a list of specific actions the skill performs, matching the 'domain + 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

There is an explicit trigger ('Ativado ao configurar...') so it is not capped, but the 'what' is largely indistinguishable from the 'when' (it describes the configuration scenario rather than what the skill does), giving a clear but weak 'what'.

3 / 5

Trigger Term Quality

Terms like 'autenticação', 'autorização', 'JWT Bearer', 'Roles', 'Políticas de Acesso' are relevant and real, but the set is jargon-heavy with no synonym or variation coverage, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The combination of .NET 8, API vertical slices, and JWT/Roles/Policies is a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.