agentsclimarketplace

404 frameworks quarkus security

Skill jabrena/plinth/skills/404-frameworks-quarkus-security

Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.

Install
npx -y skills add jabrena/plinth --skill 404-frameworks-quarkus-security

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.7 KB, as published. Nobody here has run it

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.

  1. Gather scope and decide target improvements

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

  1. Apply framework-aligned changes

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

  1. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.