CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quarkus-security

Quarkus security implementation patterns: JWT and OIDC authentication, @RolesAllowed RBAC and SecurityIdentity checks, Bean Validation and custom validators, parameterized Panache queries, BCrypt password hashing, CORS and security headers, rate limiting, audit logging, Vault or environment-variable secrets, and dependency CVE scanning. Use when adding authentication or authorization, validating input, managing secrets, or hardening a Quarkus application.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 delivers dense, mostly executable Quarkus security patterns with excellent signal-to-token ratio and only trivial placeholder gaps. Its weaknesses are structural: no workflow sequencing or validation checkpoints, and a large monolithic body with no reference-file split.

Suggestions

Replace the placeholder validateToken() method and the BAD native-query fragment with complete, executable examples so every snippet is copy-paste ready.

Split per-topic pattern libraries (custom validators, rate limiting, Vault integration, audit logging) into one-level-deep references/*.md files, keeping SKILL.md as a concise overview with clearly signaled links.

Add a short sequenced workflow with validation checkpoints (e.g., add auth -> verify token rejection for missing/invalid credentials -> confirm @RolesAllowed returns 403) and expand 'Test authentication and authorization paths' into concrete test commands or examples.

DimensionReasoningScore

Conciseness

The body is lean and code-first with almost no explanatory padding (it never explains what Quarkus or JWT is), but several full class listings carry boilerplate (imports, unrelated endpoints) that could be trimmed to the relevant fragment, keeping it just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Nearly all guidance is copy-paste-ready: complete resource classes, application.properties blocks, and concrete commands ('mvn org.owasp:dependency-check-maven:check'). It misses a 5 because validateToken(token) is a 'return true' placeholder with '// Token validation logic' and the BAD native-query snippet is a non-executable fragment.

4 / 5

Workflow Clarity

The skill is a topic-organized pattern reference with no sequenced workflow and no validation checkpoints — the only validation guidance is the vague 'Test authentication and authorization paths' bullet. This matches the anchor for present-but-implicit structure with checkpoint gaps rather than the clear-sequence-with-most-checkpoints anchor.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers and a 'When to Activate' index, but the ~460-line body inlines everything with no references/ split — per-topic code (e.g., full validator, rate limiter, Vault integration examples) could live in one-level-deep reference files. This is the could-be-better-organized anchor, not the good-structure-with-minor-gaps anchor, since no progressive disclosure exists at all for a body this size.

3 / 5

Total

14

/

20

Passed

Description

92%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 strong description: comprehensive, concrete, third-person, with an explicit and specific 'Use when...' trigger clause. Only minor room for improvement in natural synonym coverage.

DimensionReasoningScore

Specificity

The description enumerates ten-plus concrete, named actions — 'JWT and OIDC authentication, @RolesAllowed RBAC and SecurityIdentity checks, Bean Validation and custom validators, parameterized Panache queries, BCrypt password hashing, CORS and security headers, rate limiting, audit logging, Vault or environment-variable secrets, and dependency CVE scanning' — comprehensive coverage of the domain with no vague filler.

5 / 5

Completeness

Explicitly answers both questions: the 'what' is the detailed pattern list, and the 'when' is a concrete 'Use when adding authentication or authorization, validating input, managing secrets, or hardening a Quarkus application' clause.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'adding authentication or authorization, validating input, managing secrets, hardening a Quarkus application', plus JWT, OIDC, BCrypt, CORS, CVE. A few common user phrasings are missing (e.g., 'login', 'permissions', 'SQL injection'), so it falls just short of the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Quarkus is named in both the capability list and the trigger clause, establishing a clear niche with distinct triggers and minimal conflict risk against generic Java security skills.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/quarkus-security/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.