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 securit
SkillScore86Maintained
Automatic
◆Security & AppSec pack
Last verified 8/20/2026
What it changes
Passed 17 of 20 test cases with the skill, and 15 of 20 without it.
Without skill73%
With skill86%
Checks it passed that the model alone missed
The response halts execution immediately without making code changes.
The response specifies running a compilation step before modifying code.
The response halts the workflow immediately if pre-change compilation fails.
and 1 more in the full report
3 fixed16 passed either way3 still failing0 broke
Pass-rate lift
+14 pp
Tokens
-12%
Agent turns
0%
Response time
-33%
Model gemini-3.6-flashMeasured 8/20/2026v119 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Before applying security configuration updates to a Quarkus service, we run `./mvnw compile`. The compilation step fails with missing dependency errors in an unrelated module. How should the security modification workflow handle this compilation failure?
What was checked, without and with the skill
Checked
Without skill
With skill
The response halts execution immediately without making code changes.
Missed
Passed
case-22 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md54 lines2 files
Quarkus Security Guidelines
Apply Quarkus security best practices with secure-by-default API and service boundaries.
What is covered in this Skill?
Quarkus security configuration for authentication mechanisms
Authorization with @RolesAllowed / @Authenticated / @PermitAll
Endpoint and resource protection strategy
Least-privilege role design
Secure denial/error handling behavior
Sensitive data protection in logs and responses
Scope: Apply recommendations based on the reference rules and good/bad examples.
Constraints
Before applying security changes, ensure the project compiles. After improvements, run full verification.
MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed rules and examples
When to use this skill
Add Quarkus security support
Review Quarkus security configuration
Improve API authorization in Quarkus
Add JWT/OIDC security in Quarkus
Harden Quarkus authorization rules
Implement SecurityIdentity checks in Quarkus services
Workflow
Read reference and assess project context
Read references/404-frameworks-quarkus-security.md and inspect the current project setup before proposing changes.
Use when you need Kafka messaging in Quarkus with SmallRye Reactive Messaging — including channel/topic design, build-time Jackson serialization, typed @Channel/@Incoming, ack/failure strategies, retries/DLQ, idempotency, Dev Services, and Testcontainers integration tests. This should trigger for requests such as Add Kafka in Quarkus; Review Reactive Messaging consumers; Improve failure handling for Quarkus Kafka; Configure Quarkus Reactive Messaging Kafka channels; Add Quarkus Kafka failure str