400-frameworks-quarkus-create-project

Use when you need to create a new Maven-based Quarkus 3.x project using SDKMAN-managed Java and Quarkus CLI tooling. This should trigger for requests such as Create a Quarkus Maven project; Bootstrap Quarkus project with SDKMAN; Generate a new Quarkus service; Create Quarkus 3 Maven project; Scaffold Quarkus service with Java 25. Part of Plinth Toolkit

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The content is highly actionable with a clear, validated workflow and concrete executable commands throughout. The only notable gap is progressive disclosure: a bundle reference file exists but is not linked from the SKILL.md body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and tight constraint bullets, but the 'Role' persona line and the 'Goal' restatement of the steps are minor over-explanation that could be trimmed.	4 / 5
Actionability	Steps give fully executable commands including a copy-paste-ready 'quarkus create app <group>:<artifact>:<version> --maven --java=25 ...' example and specific SDKMAN/Maven verify commands covering the common cases.	5 / 5
Workflow Clarity	A clear six-step sequence includes explicit validation (Step 5 './mvnw clean verify', the VERIFY constraint, target-directory pre-check) and error-recovery guidance to report the failing goal and next corrective action, satisfying the feedback-loop expectation for a filesystem-changing operation.	5 / 5
Progressive Disclosure	Sections are well-organized and the body is self-contained, but the provided bundle file references/400-frameworks-quarkus-create-project.md is never linked or signaled from the body, leaving an orphaned reference and a minor navigation gap.	4 / 5
	Total	18 / 20 Passed

Description

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

The description is specific and clearly niche-targeted with an explicit 'Use when' trigger, but it under-utilizes trigger synonyms and lists only one action verb. Adding varied natural trigger phrases and a fuller action list would push it toward the top anchor.

Suggestions

Add natural trigger-phrase variations users actually say — e.g. 'scaffold', 'bootstrap', or 'generate a new Quarkus service' — to broaden trigger term coverage beyond the single verb 'creating'.

Enumerate the concrete actions the skill performs (verify SDKMAN/Java, install or switch CLI candidates, create the Maven project, verify with Maven) so specificity reaches the multi-action anchor.

Separate the 'what' (capability) from the 'when' (trigger scenarios) more distinctly, listing several concrete triggering requests as the reference file already does.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — 'creating a new Maven-based Quarkus 3.x project' with 'SDKMAN-managed Java and Quarkus CLI tooling' — but does not enumerate multiple distinct actions, so it sits at 'names domain and 1-2 concrete actions' rather than the multi-action level 4.	3 / 5
Completeness	It has an explicit 'Use when' clause and a clear capability statement, answering both what and when, but the 'when' relies on a single trigger scenario rather than the varied concrete trigger phrases that define level 5.	4 / 5
Trigger Term Quality	It covers good natural domain keywords ('Quarkus 3.x project', 'Maven', 'SDKMAN', 'Java', 'Quarkus CLI') but only the single verb 'creating', omitting common synonyms a user would say such as 'scaffold', 'bootstrap', or 'generate'.	4 / 5
Distinctiveness Conflict Risk	The combination of 'Quarkus 3.x', 'Maven-based', and 'SDKMAN-managed' carves a clear niche with distinct triggers and minimal overlap risk against generic Java or Gradle project skills.	5 / 5
	Total	16 / 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: jabrena/plinth
Path: skills/400-frameworks-quarkus-create-project/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.