Skip to main content
skill CX Codex

404-frameworks-quarkus-security — Quarkus Security skill for Claude Code

404-frameworks-quarkus-security is a skill for designing and reviewing security in Quarkus applications, including authentication, access control, and secure logging.

Apache-2.0 294 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 404-frameworks-quarkus-security -a claude-code
Open on GitHub

What 404-frameworks-quarkus-security does

The skill provides guidance and patterns for Quarkus Security: configuring authentication mechanisms, applying @RolesAllowed, @Authenticated, and @PermitAll to protect endpoints, designing least-privilege roles, and handling auth failures safely. It covers SecurityIdentity checks in services and secure logging practices without exposing sensitive data.

Before applying changes, verify the project compiles by running ./mvnw compile or mvn compile. After improvements, run ./mvnw clean verify or mvn clean verify for full verification. The skill is part of the Plinth Toolkit.

What it helps with

  • Set up JWT or OIDC authentication in Quarkus
  • Review and strengthen REST API authorization
  • Apply role-based access control with annotations
  • Protect endpoints from unauthorized requests
  • Handle authentication failures securely

Example prompts for the agent

  • Add JWT authentication to this Quarkus REST API
  • Review Quarkus security configuration in the project
  • Strengthen authorization with @RolesAllowed on protected resources

How to install 404-frameworks-quarkus-security

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 404-frameworks-quarkus-security -a claude-code

2Manually: put the files in place

~/.claude/skills/404-frameworks-quarkus-security/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/404-frameworks-quarkus-security/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 404-frameworks-quarkus-security

How do I install 404-frameworks-quarkus-security in Claude Code?

Run npx skills add jabrena/plinth --skill 404-frameworks-quarkus-security -a claude-code. The skill will then be available at ~/.claude/skills/404-frameworks-quarkus-security/SKILL.md.

What does the 404-frameworks-quarkus-security skill do?

The skill assists in securing Quarkus applications: setting up authentication (JWT, OIDC, basic auth), managing roles and permissions through annotations, preventing sensitive data exposure in logs, and handling authentication errors correctly.

What do I need to use this skill?

Your project must compile with Maven: ./mvnw compile or mvn compile. After making changes, run ./mvnw clean verify or mvn clean verify to verify the improvements.

Source text

SKILL.md · Apache-2.0
---
name: 404-frameworks-quarkus-security
description: 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
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# 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

1. **Read reference and assess project context**

Read `references/404-frameworks-quarkus-security.md` and inspect the current project setup before proposing changes.

2. **Gather scope and decide target improvements**

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

3. **Apply framework-aligned changes**

Implement or refactor security-related configuration/code following the reference patterns and project conventions.

4. **Run verification and report results**

Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.

## Reference

For detailed guidance, examples, and constraints, see [references/404-frameworks-quarkus-security.md](references/404-frameworks-quarkus-security.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Security →

From the same set123

The whole set →
703-technologies-fuzzing-testing The 703-technologies-fuzzing-testing skill guides CATS-based fuzz testing for Java APIs from an OpenAPI contract. Use it to probe invalid inputs, boundary conditions, and CI checks. CX Codex +1 304installs 314-frameworks-spring-kafka 314-frameworks-spring-kafka guides Kafka messaging setup in Spring Boot projects, covering consumers, DLT retries, and Testcontainers. CX Codex +1 297installs 182-java-observability-metrics-micrometer 182-java-observability-metrics-micrometer guides Java developers through Micrometer metrics design and validation. Use it when adding service measurements or revising existing instrumentation. CX Codex +1 297installs 403-frameworks-quarkus-validation 403-frameworks-quarkus-validation guides Quarkus validation work, from DTO constraints and REST boundaries to configuration checks and API error mapping. CX Codex +1 296installs 315-frameworks-spring-mongodb 315-frameworks-spring-mongodb — a skill for designing and implementing MongoDB data access in Spring Boot. Covers document modeling, repositories, indexing, optimistic locking, and error handling strategies. CX Codex +1 284installs 504-frameworks-micronaut-security The 504-frameworks-micronaut-security skill reviews and improves Micronaut application security, covering authentication, route authorization, JWT, CORS, and safe handling of sensitive data. CX Codex +1 282installs 503-frameworks-micronaut-validation 503-frameworks-micronaut-validation guides validation setup in Micronaut applications, from Bean Validation annotations to HTTP 400 error payloads. CX Codex +1 280installs 414-frameworks-quarkus-kafka 414-frameworks-quarkus-kafka guides Kafka messaging setups in Quarkus using SmallRye Reactive Messaging. Useful for channel tuning, serialization, and DLQ failure handling. CX Codex +1 279installs

Project sponsors

Companies that keep this analytics open