Imported from jabrena/plinth (skills/404-frameworks-quarkus-security/SKILL.md). Install upstream with npx skills add jabrena/plinth --skill 404-frameworks-quarkus-security. Copyright stays with the author (Apache-2.0).

Quarkus Security Guidelines

Name: 404-frameworks-quarkus-security
Author: jabrena

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.

Gather scope and decide target improvements

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

Apply framework-aligned changes

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

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.

{ "ocm": "1", "id": "jabrena-plinth-404-frameworks-quarkus-security", "kind": "skill", "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", "publisher": "jabrena", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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" ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/jabrena/plinth", "path": "skills/404-frameworks-quarkus-security/SKILL.md", "ref": "HEAD", "url": "https://github.com/jabrena/plinth/blob/HEAD/skills/404-frameworks-quarkus-security/SKILL.md", "key": "jabrena/plinth/skills/404-frameworks-quarkus-security/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# Quarkus Security Guidelines\n\nApply Quarkus security best practices with secure-by-default API and service boundaries.\n\n**What is covered in this Skill?**\n\n- Quarkus security configuration for authentication mechanisms\n- Authorization with @RolesAllowed / @Authenticated / @PermitAll\n- Endpoint and resource protection strategy\n- Least-privilege role design\n- Secure denial/error handling behavior\n- Sensitive data protection in logs and responses\n\n**Scope:** Apply recommendations based on the reference rules and good/bad examples.\n\n## Constraints\n\nBefore applying security changes, ensure the pro", "cost": { "context_tokens": 504 } }

404-frameworks-quarkus-security

About

Quarkus Security Guidelines

Constraints

When to use this skill

Workflow

Reference

Use it

Manifest

Reviews