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

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

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

A concise, well-structured skill body with strong validation-gated workflow and clean single-reference progressive disclosure. The only gap is that executable code patterns are deferred to the reference rather than shown inline.

Dimension	Reasoning	Score
Conciseness	Lean, well-organized body with no padded explanations of what CDI or Quarkus is; every section (coverage list, constraints, when-to-use, workflow, reference) earns its place and assumes Claude's competence.	5 / 5
Actionability	Gives concrete executable commands ("./mvnw compile", "mvn clean verify") and a specific reference path, but the actual code patterns live in the reference rather than inline, leaving minor gaps in directly executable guidance.	4 / 5
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints and a hard feedback loop — MANDATORY compile before changes, blocking on failure, and a VERIFY step after — matching the top anchor for sequenced validation.	5 / 5
Progressive Disclosure	SKILL.md is an overview pointing to a single real, clearly-signaled one-level-deep reference (references/401-frameworks-quarkus-core.md, linked twice), with content appropriately split and easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that names concrete capabilities and provides explicit trigger guidance in third person. Minor polish could remove the stray "; " typo and the trailing "Part of Plinth Toolkit" tagline.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capability areas — "CDI beans and scopes", "SmallRye Config and profiles", "lifecycle, interceptors and events", "virtual threads", "test-friendly design" — giving comprehensive coverage rather than a single vague action.	5 / 5
Completeness	Explicitly answers both what ("building or reviewing core Quarkus applications with CDI beans and scopes...") and when ("Use when... This should trigger for requests such as...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrasings a user would say ("Review Java code for Quarkus application structure and CDI", "Apply best practices for Quarkus configuration and beans"), with good keyword coverage though a few synonyms or .java/extension cues are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Quarkus core / CDI) with distinct, domain-specific triggers, making overlap with unrelated skills unlikely.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/401-frameworks-quarkus-core/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.