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. ; Review Quarkus CDI bean lifecycle and configuration. Part of Plinth Toolkit

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/401-frameworks-quarkus-core/SKILL.md
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 content is well-structured with a clear, validated workflow and exemplary one-level-deep progressive disclosure pointing to a real reference file. Its main gaps are minor redundancy in the Constraints section and the absence of any executable code examples in the body itself, with all code living in the reference.

Suggestions

Collapse the MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION bullets into a single concise compile-gate statement to remove redundancy and recover a conciseness point.

Include at least one small inline code example (e.g. a minimal @QuarkusMain entry point or @ApplicationScoped constructor-injection bean) so the body is actionable on its own without forcing a reference read for the common case.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's Quarkus/CDI knowledge, but the Constraints section restates the same compile-first/stop-on-failure idea across MANDATORY, PREREQUISITE, SAFETY, and BLOCKING CONDITION bullets, which is redundant padding that could be tightened.

2 / 3

Actionability

It gives concrete commands (./mvnw compile, ./mvnw clean verify) and a named reference to read, but the body itself contains no executable code examples — all code is delegated to the reference file — leaving it as guidance rather than copy-paste-ready instruction.

2 / 3

Workflow Clarity

A clear four-step workflow is sequenced with explicit validation checkpoints (MANDATORY compile before, VERIFY clean verify after) and a blocking stop-on-failure condition, matching the rubric's clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The body is a concise overview that signals a single one-level-deep reference (references/401-frameworks-quarkus-core.md, which exists) in both the Workflow and Reference sections, with content appropriately split out rather than inlined.

3 / 3

Total

10

/

12

Passed

Description

90%

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 is comprehensive and well-triggered, clearly answering both what it does and when to use it with concrete, natural phrasings. Its only real weakness is voice: it uses imperative/second-person framing ('Use when building...') rather than the third-person voice the rubric expects, which costs it a specificity point.

Suggestions

Rewrite the description in third-person voice (e.g. 'Reviews and builds core Quarkus applications with CDI beans... Use when the user asks to review Quarkus application structure...') to satisfy the rubric's voice expectation and recover the specificity point.

Tighten the trailing trigger list slightly — the final 'Review Quarkus CDI bean lifecycle and configuration' near-duplicates earlier phrasings and could be merged to reduce redundancy.

DimensionReasoningScore

Specificity

Lists many concrete capabilities (CDI beans/scopes, SmallRye Config, interceptors, events, virtual threads) which would anchor at 3, but the description uses imperative/second-person voice ('Use when building...') rather than third person, triggering the rubric's -1 specificity penalty.

2 / 3

Completeness

Clearly states what the skill covers (core Quarkus CDI, config, lifecycle, virtual threads) and provides an explicit 'Use when...' clause with several concrete triggering requests, answering both what and when.

3 / 3

Trigger Term Quality

Includes natural user phrasings such as 'Review Java code for Quarkus application structure and CDI', 'Apply best practices for Quarkus configuration and beans', and 'Add virtual-thread configuration or tune CDI lifecycle', giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to Quarkus core CDI/configuration/lifecycle concerns with distinct Quarkus-specific trigger language, making it unlikely to fire for unrelated skills.

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.

Validation16 / 16 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.