Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-organized, concise skill body with clear workflow sequencing, validation, and clean one-level progressive disclosure to a real reference file. Its only gap is actionability: the primary project-creation command is abstracted out of the body into the reference.
Suggestions
Include the concrete 'quarkus create app <group>:<artifact>:<version> --maven --java=25 --package-name=... --extension=...' command (or a copy-paste snippet) in the body's create step so the core action is executable without opening the reference.
Add a brief fix-and-retry feedback note to the verify step (e.g., on failure, correct the reported goal and re-run './mvnw clean verify') to make the validation loop explicit in the body rather than only in the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what Quarkus, Maven, or SDKMAN are, and every section (constraints, workflow, reference) earns its place. | 3 / 3 |
Actionability | Some concrete commands are present ('sdk version', './mvnw clean verify', 'mvn clean verify') but the core creation step is only abstractly described ('Use the Quarkus CLI to create a Maven project'), delegating the executable command to the reference. | 2 / 3 |
Workflow Clarity | A clear four-step sequence (gather inputs, verify tooling, create, verify and report) with an explicit validation checkpoint ('Run Maven verification', './mvnw clean verify'), matching the anchor for clear sequencing with validation. | 3 / 3 |
Progressive Disclosure | The body is a concise overview pointing to a single, real, one-level-deep reference (references/400-frameworks-quarkus-create-project.md), clearly signaled via a Reference section, a 'BEFORE APPLYING' note, and the workflow's first step. | 3 / 3 |
Total | 11 / 12 Passed |