quarkus-app

Use this skill whenever a user wants to create, scaffold, bootstrap, initialize, generate, or set up a new Quarkus application or microservice. Also trigger when a user asks how to add extensions to an existing Quarkus project, upgrade a Quarkus version, or maintain a Quarkus app's dependencies. This skill ensures all projects are generated using the latest official Quarkus platform version, proper tooling (CLI preferred, Maven plugin as fallback), and official platform or Quarkiverse extensions only. Trigger even for casual phrasing like "spin up a Quarkus app", "start a new Quarkus service", "create a Quarkus REST API", or "add a Quarkus extension".

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 strong, actionable body with copy-paste-ready commands, a clear numbered workflow, and well-placed one-level-deep references to real bundle files. The only weaknesses are minor: a few redundant prose lines that could be trimmed and the absence of an error-recovery feedback loop in the workflow.

Suggestions

Remove the redundant Java-version prose under Step 1 ('If the user hasn't specified a Java version, ask which version they'd like to use and suggest 25 as the default') since the table already notes 'Always ask — suggest 25 as the default'.

Add a brief error-recovery step after project generation (e.g., what to do if `quarkus create` fails or an extension short name cannot be resolved) to close the validation gap in the workflow.

Trim the generic opener 'Always follow the decision tree and conventions below.' — the sectioned structure already makes this obvious.

Dimension	Reasoning	Score
Conciseness	Largely lean and action-oriented with no padding about what Quarkus/Maven are, but contains minor trimmable redundancy — e.g., the Java-version default is stated both in the Step 1 table ("Always ask — suggest 25 as the default") and repeated in prose immediately below, and the opening "Always follow the decision tree and conventions below" line adds little.	4 / 5
Actionability	Fully executable, copy-paste-ready commands for both CLI and Maven-plugin paths, with canonical examples (REST+PostgreSQL, AI/LangChain4j, Kafka) covering the common generation cases and concrete post-generation/dev-mode guidance.	5 / 5
Workflow Clarity	A clear Step 0–5 sequence with an explicit validation checkpoint at Step 0 (verify the latest Quarkus version before generating), but it lacks an error-recovery feedback loop for what to do if creation or extension resolution fails, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Well-signaled, one-level-deep references to real bundle files — "See `references/extensions.md`" and "see `references/rhbq.md`" — with the bulk of action guidance kept inline in clearly organized sections, making navigation easy.	5 / 5
	Total	18 / 20 Passed

Description

100%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.

An excellent description that clearly states what the skill does, when to trigger it, and uses natural phrasing a user would actually say. Third-person voice is maintained throughout, and the Quarkus-specific framing makes it highly distinct.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "create, scaffold, bootstrap, initialize, generate, or set up a new Quarkus application", "add extensions", "upgrade a Quarkus version", "maintain a Quarkus app's dependencies" — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what (create/maintain Quarkus apps, add extensions, upgrade versions) and when ("Use this skill whenever a user wants to...", "Also trigger when...", "Trigger even for casual phrasing like...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-language coverage including casual phrasing users actually say: "spin up a Quarkus app", "start a new Quarkus service", "create a Quarkus REST API", "add a Quarkus extension", plus synonyms (application/microservice) and the technical term "extensions".	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Quarkus specifically) with distinct, domain-specific triggers that are unlikely to fire for other skills; the Quarkus-only framing keeps conflict risk minimal.	5 / 5
	Total	20 / 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: jeremyrdavis/agentic-skills-for-quarkus
Path: skills/quarkus-app/SKILL.md
Commit: 393c86e

Reviewed: 5 days 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.