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, health probes, virtual threads, and test-friendly design. Part of the skills-for-java project
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 excellent trigger term coverage and clear distinctiveness for Quarkus development. The main weakness is that it lists technology areas rather than concrete actions (e.g., 'configure CDI scopes' vs just 'CDI beans and scopes'). The 'Use when' clause is present and effective, though the trailing 'Part of the skills-for-java project' adds no value for skill selection.
Suggestions
Replace feature category nouns with action verbs: 'Configure CDI beans and scopes, manage SmallRye Config profiles, implement health probes' instead of just listing the topics.
Remove 'Part of the skills-for-java project' as it doesn't help Claude select this skill and wastes description space.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Quarkus applications) and lists several specific areas (CDI beans, SmallRye Config, lifecycle, interceptors, health probes, virtual threads), but these are feature categories rather than concrete actions like 'create', 'configure', or 'debug'. | 2 / 3 |
Completeness | Has explicit 'Use when' clause that covers both building and reviewing scenarios, and lists specific trigger contexts (CDI beans, config, lifecycle, etc.). Clearly answers both what (core Quarkus applications with listed features) and when (building or reviewing). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Quarkus', 'CDI beans', 'scopes', 'SmallRye Config', 'profiles', 'interceptors', 'events', 'health probes', 'virtual threads'. These are terms developers naturally use when working with Quarkus. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Quarkus-specific terminology (CDI, SmallRye Config, health probes). The combination of these specific technologies creates a clear niche that wouldn't conflict with generic Java or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 as an overview document with excellent workflow clarity and appropriate progressive disclosure. The constraints section provides clear validation checkpoints. However, the skill lacks any concrete code examples, relying entirely on the reference file for actionable implementation details, which reduces its standalone utility.
Suggestions
Add 1-2 minimal executable code examples for the most common patterns (e.g., @ApplicationScoped bean with constructor injection, or a basic @ConfigMapping example)
Include a quick-start snippet showing a typical CDI bean setup that can be copy-pasted and adapted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, listing covered topics as bullet points without explaining what CDI, SmallRye, or other concepts are. It assumes Claude's competence with Quarkus and Java frameworks. | 3 / 3 |
Actionability | Provides clear constraints and verification commands (./mvnw compile, ./mvnw clean verify), but lacks concrete code examples. All actual implementation guidance is deferred to the reference file rather than providing copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile before changes, stop on failure, verify after changes. The blocking condition and safety constraints create a proper feedback loop for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections (What is covered, Constraints, When to use, Reference). Appropriately delegates detailed guidance to a single reference file with clear signaling. | 3 / 3 |
Total | 11 / 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
16eb4bf
- 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.