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. Part of cursor-rules-java project

Quality

62%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/400-frameworks-quarkus-create-project/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is well-structured in terms of layout and constraints but critically lacks actionability — there are no concrete CLI commands, code snippets, or copy-paste-ready examples in the body itself. Nearly all useful content is deferred to a reference file that wasn't provided, making the SKILL.md function more as a table of contents than an actionable guide. The workflow steps read as descriptions of what to do rather than instructions on how to do it.

Suggestions

Add concrete, executable CLI commands inline in the workflow steps (e.g., `sdk install java 25-open`, `quarkus create app --maven --group-id=com.example ...`, `./mvnw clean verify`) so the skill is actionable without requiring the reference file.

Include at least one complete end-to-end example showing the exact commands from SDKMAN verification through project creation and Maven verification.

Add explicit error recovery guidance in the workflow, such as what to do if `sdk version` fails or if `./mvnw clean verify` fails, to improve workflow clarity.

Remove the 'What is covered in this Skill?' bullet list as it largely duplicates the workflow section and adds unnecessary tokens.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('What is covered in this Skill?' bullet list largely restates the workflow) and could be tightened. The constraints section is reasonably lean but the overall structure has redundancy between the summary bullets, workflow steps, and 'When to use' section.	2 / 3
Actionability	The skill provides no executable commands or concrete code examples. The workflow steps are abstract descriptions ('Use the Quarkus CLI to create a Maven project') rather than actual CLI commands. All concrete guidance is deferred to the reference file, making the skill itself vague and non-actionable.	1 / 3
Workflow Clarity	The four workflow steps are logically sequenced and include a verification step (step 4), but they lack concrete commands, explicit validation checkpoints with feedback loops, and specific error recovery guidance. The verification step says 'run Maven verification' without showing the actual command inline in the workflow.	2 / 3
Progressive Disclosure	The skill references a single external file for detailed guidance, which is a reasonable one-level-deep structure. However, since no bundle files were provided, we cannot verify the reference exists or is well-structured. The skill itself defers too much content to the reference, leaving the main body too thin to be useful on its own.	2 / 3
	Total	7 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description with strong trigger terms and clear completeness, explicitly stating both what the skill does and when to use it. Its main weakness is that the capability described is essentially a single action (project creation/bootstrapping) stated in multiple ways, rather than listing multiple distinct concrete actions. The description is well-targeted and distinctive for its niche.

Suggestions

Add more specific concrete actions beyond project creation, such as 'configures extensions, sets up dev services, generates REST endpoints' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (Maven-based Quarkus 3.x project) and mentions specific tooling (SDKMAN, Quarkus CLI), but doesn't list multiple concrete actions beyond 'create/bootstrap/generate a new project'. It's essentially one action described three ways.	2 / 3
Completeness	Clearly answers both 'what' (create a new Maven-based Quarkus 3.x project using SDKMAN-managed Java and Quarkus CLI) and 'when' (explicit 'Use when' clause and 'This should trigger for' with example phrases).	3 / 3
Trigger Term Quality	Good coverage of natural trigger terms: 'Maven', 'Quarkus', 'SDKMAN', 'Bootstrap', 'Generate', 'Quarkus service', 'Quarkus Maven project'. These are terms users would naturally use when requesting this kind of project setup.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Quarkus 3.x + Maven + SDKMAN is a very specific combination unlikely to conflict with other skills. The mention of specific tooling (SDKMAN, Quarkus CLI) further narrows the scope.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: b73c9d3

Reviewed: 4 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.