404-frameworks-quarkus-security

Use when you need to design, review, or improve security in Quarkus applications — including Quarkus Security with JWT/OIDC, basic auth, @RolesAllowed / @Authenticated / @PermitAll, SecurityIdentity, permission checks, path-based authorization in configuration, exception mapping for auth failures, and sensitive-data-safe logging. This should trigger for requests such as Add Quarkus security support; Review Quarkus security configuration; Improve API authorization in Quarkus; Add JWT/OIDC security in Quarkus; Harden Quarkus authorization rules. Part of Plinth Toolkit

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 well-structured, concise SKILL.md that delegates detail to a real reference file and includes strong validation checkpoints. Its main weakness is actionability: the body relies on the reference for the concrete executable security patterns.

Suggestions

Add 1-2 short inline code examples (e.g., a minimal @RolesAllowed/@PermitAll resource or an application.properties auth.permission snippet) so the body is actionable before the reference is consulted.

State the single most important secure-by-default rule inline (e.g., 'annotate resources authenticated-by-default, then @PermitAll for public endpoints') as a quick reference.

Link the reference earlier in the Workflow's step 1 with a one-line note of what each section contains, to improve navigation.

Dimension	Reasoning	Score
Conciseness	Lean ~50-line overview with no padding and no explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides concrete build/verify commands and a clear workflow, but the actual executable security code and patterns are delegated to the reference file rather than appearing inline, leaving key implementation details out of the body.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit MANDATORY/SAFETY/VERIFY validation checkpoints and a stop-on-failure rule, covering build-before and verify-after; feedback loops for the destructive/verification-heavy operation are present.	5 / 5
Progressive Disclosure	Clear overview pointing to a single one-level-deep reference file (references/404-frameworks-quarkus-security.md, which exists) that is well-signaled, with content appropriately split between body and reference.	5 / 5
	Total	18 / 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, specific description that clearly states both what the skill does and when it should trigger, using natural user phrasing. Minor trigger-term breadth could be expanded but it is otherwise exemplary.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — JWT/OIDC, basic auth, @RolesAllowed/@Authenticated/@PermitAll, SecurityIdentity, path-based authz, exception mapping, sensitive-data logging — giving comprehensive coverage of design/review/improve actions.	5 / 5
Completeness	Explicitly answers 'what' (the enumerated Quarkus security mechanisms) and 'when' ('This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases a user would say are present ('Add Quarkus security support', 'Review Quarkus security configuration', 'Harden Quarkus authorization rules') with good synonyms, though a few natural variations are missing; not a 5 because coverage is strong but not exhaustive of synonyms.	4 / 5
Distinctiveness Conflict Risk	Clearly niched to Quarkus security via specific annotations and mechanisms, with distinct triggers and minimal overlap risk; the 'Part of Plinth Toolkit' tail does not meaningfully broaden it.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: jabrena/plinth
Path: skills/404-frameworks-quarkus-security/SKILL.md
Commit: 05bf9d1

Reviewed: 8 minutes ago

Table of Contents

Discovery Implementation Validation

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.