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. This should trigger for requests such as Review Java code for Quarkus application structure and CDI; Apply best practices for Quarkus configuration and beans; Improve CDI interceptors, events, or programmatic injection in Quarkus; Add virtual-thread configuration or tune CDI lifecycle. Part of cursor-rules-java project
80
75%
Does it follow best practices?
Impact
—
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
100%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 strong skill description that clearly defines its scope around core Quarkus application development with specific technologies. It provides both 'what' and 'when' guidance with explicit trigger examples, and uses domain-specific terminology that developers would naturally use. The description is well-structured and distinctive enough to avoid conflicts with other Java or framework-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. The trigger examples further enumerate specific actions like reviewing code, applying best practices, improving interceptors, and adding virtual-thread configuration. | 3 / 3 |
Completeness | Clearly answers both 'what' (building/reviewing Quarkus applications with CDI, config, interceptors, virtual threads, etc.) and 'when' with an explicit 'Use when...' clause at the start plus a 'This should trigger for requests such as...' section providing concrete trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Quarkus', 'CDI', 'beans', 'scopes', 'SmallRye Config', 'profiles', 'interceptors', 'events', 'virtual threads', 'lifecycle', 'programmatic injection'. These are terms a Java/Quarkus developer would naturally use when requesting help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: core Quarkus application structure with specific technologies (CDI, SmallRye Config, virtual threads). The combination of Quarkus + CDI + SmallRye Config creates a very specific domain unlikely to conflict with other skills, even other Java-related ones. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable high-level structure for Quarkus core guidelines with clear trigger conditions and a compilation safety gate. However, it lacks concrete code examples (all deferred to a reference file), repeats the compilation constraint excessively, and the workflow steps are too generic to be highly actionable on their own. The skill functions primarily as a pointer to the reference file rather than a self-contained actionable guide.
Suggestions
Add at least 2-3 concrete, executable code snippets (e.g., a @ConfigMapping example, a CDI interceptor pattern) directly in the SKILL.md to improve actionability without requiring the reference file for basic tasks.
Consolidate the five redundant compilation-check bullet points in Constraints into a single clear directive, e.g., '**Pre-check**: Run `./mvnw compile` — if it fails, stop and ask the user to fix compilation errors before proceeding.'
Add an explicit feedback loop in the workflow for when `./mvnw clean verify` fails after applying changes (e.g., 'If verification fails: review errors, revert or fix, re-run verify before reporting').
Trim the 'What is covered' bullet list to 4-5 high-level categories and move the detailed topic enumeration into the reference file.
| 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 compilation-check idea five different ways (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION, VERIFY). The skill could be tightened significantly. | 2 / 3 |
Actionability | The skill provides concrete commands (`./mvnw compile`, `./mvnw clean verify`) and references a detailed file, but contains no executable code examples, no concrete before/after patterns, and no specific CDI or config snippets. All substantive guidance is deferred to the reference file. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced and includes a pre-check (compile) and post-check (verify), which is good. However, the steps are quite generic ('apply framework-aligned changes') with no validation checkpoints between steps 2 and 3, and no explicit error-recovery/feedback loop if verification fails after changes are applied. | 2 / 3 |
Progressive Disclosure | The skill correctly references a single detailed file (references/401-frameworks-quarkus-core.md) for deeper content, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists, and the SKILL.md itself contains a long inline bullet list of topics that could arguably be in the reference rather than the overview. The 'What is covered' section is borderline inline bloat. | 2 / 3 |
Total | 8 / 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
ef4eba3
- 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.