CtrlK
BlogDocsLog inGet started
Tessl Logo

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

70

Quality

85%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill has strong workflow structure with clear validation checkpoints and good progressive disclosure to a reference file. However, it is weakened by redundant constraint statements, an overly detailed topic listing that doesn't add actionable value, and a complete absence of inline code examples — all concrete guidance is deferred to the reference file, making the skill itself more of a table of contents than an actionable guide.

Suggestions

Add at least 2-3 inline code examples showing key patterns (e.g., @ConfigMapping usage, constructor injection with @Inject, @RunOnVirtualThread annotation) so the skill is actionable without requiring the reference file for basic tasks.

Consolidate the constraints section — the compilation prerequisite is stated four different ways; reduce to a single clear statement with the commands.

Trim the 'What is covered' bullet list to just the section headers or remove it entirely, as it mostly lists CDI/Quarkus concepts Claude already understands.

DimensionReasoningScore

Conciseness

The skill includes a lengthy 'What is covered' bullet list that largely restates concepts Claude already knows about Quarkus/CDI. The constraints section is repetitive (compilation check is stated 4 different ways). However, the workflow and reference sections are reasonably lean.

2 / 3

Actionability

The skill provides concrete commands (./mvnw compile, mvn clean verify) and references a detailed guide, but lacks any executable code examples, good/bad pattern snippets, or copy-paste ready configurations. All actual guidance is deferred to the reference file.

2 / 3

Workflow Clarity

The workflow is clearly sequenced with four explicit steps: read reference, gather scope, apply changes, and verify. The constraints section establishes explicit validation checkpoints (compile before, verify after) with clear blocking conditions and error recovery guidance (stop if compilation fails).

3 / 3

Progressive Disclosure

The skill serves as a clear overview with a well-signaled one-level-deep reference to the detailed guide (references/401-frameworks-quarkus-core.md). Content is appropriately split between the overview skill and the detailed reference file, with clear navigation.

3 / 3

Total

10

/

12

Passed

Description

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 (CDI, SmallRye Config, virtual threads). It excels at providing explicit trigger guidance with example requests and uses appropriate third-person voice. The description is well-structured with both capability listing and usage triggers, making it easy for Claude to select appropriately.

DimensionReasoningScore

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 specify actions like 'Review Java code', 'Apply best practices', 'Improve CDI interceptors', 'Add virtual-thread configuration'.

3 / 3

Completeness

Clearly answers both 'what' (building/reviewing Quarkus applications with CDI, config, interceptors, virtual threads, etc.) and 'when' with explicit trigger guidance ('Use when building or reviewing...', 'This should trigger for requests such as...' with four specific example triggers).

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 developer working with Quarkus would naturally use in requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: core Quarkus application structure with CDI, SmallRye Config, and virtual threads. The specific technology stack (Quarkus + CDI + SmallRye) makes it very unlikely to conflict with generic Java or other framework skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.