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
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has a well-structured workflow with clear validation checkpoints and appropriate safety constraints for a build-oriented task. However, it lacks concrete code examples (no CDI patterns, no config snippets) making it more of a process guide than an actionable skill, and the content is somewhat verbose with redundant constraint statements and an extensive feature inventory list.
Suggestions
Add at least 2-3 concrete before/after code examples for the most common patterns (e.g., constructor injection with @Inject, @ConfigMapping usage, @ApplicationScoped vs @Singleton choice) to improve actionability.
Consolidate the constraints section—the five bullet points all express the same 'compile before, verify after' idea and could be reduced to two concise lines.
Trim or remove the 'What is covered' bullet list; it reads as a feature inventory that Claude doesn't need. Instead, let the reference file serve as the detailed catalog.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat useful as a table of contents but is verbose for a skill file—Claude doesn't need a feature inventory. The constraints section repeats the same 'compile first' idea five different ways. Could be significantly tightened. | 2 / 3 |
Actionability | The skill provides concrete commands (./mvnw compile, mvn clean verify) and references a detailed guide, but contains no executable code examples, no concrete before/after patterns, and no specific CDI code snippets. It describes what to do at a high level rather than showing how. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced with an explicit pre-check (compile), a read-reference step, apply step, and a verification step with reporting. The constraints section establishes a clear blocking condition and feedback loop (compilation failure → stop). | 3 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/401-frameworks-quarkus-core.md) for detailed rules and examples, which is good one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself includes a lengthy bullet list that could arguably live in the reference file, making the split suboptimal. | 2 / 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
3fa5789
- 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.