401-frameworks-quarkus-core
Use when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. Part of the skills-for-java project
76
69%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/401-frameworks-quarkus-core/SKILL.mdQuality
Discovery
82%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 does a good job of explicitly stating when to use the skill and listing relevant Quarkus-specific technologies as trigger terms. Its main weakness is that the capability verbs are limited to 'building or reviewing,' which is somewhat vague about the concrete actions performed. The mention of being part of a larger project hints at potential overlap with sibling skills without clearly delineating boundaries.
Suggestions
Replace generic verbs 'building or reviewing' with more specific actions like 'scaffolds CDI bean configurations, validates scope usage, configures SmallRye Config profiles, and implements interceptor patterns'.
Clarify boundaries with sibling skills in the skills-for-java project by specifying what this skill covers versus what adjacent skills handle (e.g., 'Does not cover REST endpoints, persistence, or reactive messaging').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Quarkus applications) and lists several specific areas (CDI beans and scopes, SmallRye Config, profiles, lifecycle, interceptors, events, virtual threads, test-friendly design), but these read more as topic areas than concrete actions. It lacks specific verbs describing what the skill actually does beyond 'building or reviewing'. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (building or reviewing core Quarkus applications with specific technologies) and 'when' via the 'Use when' clause at the beginning, covering building or reviewing scenarios involving the listed technologies. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'Quarkus', 'CDI beans', 'scopes', 'SmallRye Config', 'profiles', 'lifecycle', 'interceptors', 'events', 'virtual threads', and 'test-friendly design'. These are terms a Java/Quarkus developer would naturally mention when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | While 'core Quarkus applications' and the specific technologies listed help narrow the scope, the mention of being 'Part of the skills-for-java project' suggests there are sibling skills, and broad terms like 'building or reviewing' could overlap with other Quarkus-related skills in that project. The boundary between this and other Quarkus skills isn't fully clear. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a routing document to its reference file, providing a reasonable overview of topics and a compile-first safety workflow. However, it lacks any concrete code examples or actionable patterns for the CDI/config topics it covers, and the constraints section is repetitively verbose, restating the same compilation prerequisite in five slightly different ways.
Suggestions
Add at least 2-3 concise, executable code examples for the most common patterns (e.g., @ApplicationScoped bean with constructor injection, @ConfigMapping usage) so the skill is actionable without requiring the reference file for basic tasks.
Consolidate the constraints section: the compile-first requirement is stated five times in different phrasings — reduce to a single clear numbered workflow (1. compile, 2. apply changes, 3. verify, 4. if verify fails, fix and re-verify).
Add a brief feedback loop for post-change verification failure (e.g., 'If `mvn clean verify` fails after changes, review errors, revert if needed, and re-verify') to strengthen the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat useful as a table of contents but is moderately verbose. The constraints section repeats the same compile-first idea five different ways (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION). Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides concrete commands (`./mvnw compile`, `./mvnw clean verify`) for the verification workflow, but contains zero code examples, no concrete CDI patterns, and no executable guidance for the actual Quarkus core topics it claims to cover. All substantive content is deferred to the reference file. | 2 / 3 |
Workflow Clarity | There is a clear compile-before/verify-after workflow with an explicit blocking condition on compilation failure, which is good. However, the steps are not sequenced as a numbered workflow, and there's no feedback loop for what to do if `mvn clean verify` fails after applying changes. The actual process of applying improvements is vague ('read the reference'). | 2 / 3 |
Progressive Disclosure | The skill serves as a clear overview with a well-signaled one-level-deep reference to the detailed guidance file. The structure is clean: summary of topics, constraints, when-to-use, and a single reference link. This is appropriate progressive disclosure. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
1847adc
- Reviewed
Table of Contents
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.