quarkus-patterns

Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing. Use for Java Quarkus backend work with event-driven architectures. Use when building or reviewing a Quarkus service, especially with Camel messaging or Panache data access.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/quarkus-patterns/SKILL.md

Quality

Content

72%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 comprehensive, highly actionable Quarkus/Camel pattern reference with strong executable examples, weakened mainly by its monolithic single-file structure and the absence of any procedural workflow with validation checkpoints. It assumes Claude's competence and avoids concept padding.

Suggestions

Split the bulkier catalogs (Maven dependencies, Camel route examples, YAML configuration) into reference files under ./references/ and link to them one level deep from SKILL.md to improve progressive disclosure for a 700+ line skill.

Add a short end-to-end 'build a new Quarkus service' workflow with explicit validation checkpoints (e.g. run dev mode, run tests, verify native compilation) so the catalog also functions as a sequenced process.

Reduce repeated DI/logging boilerplate across service examples by stating the @RequiredArgsConstructor/@Slf4j/@Transactional convention once and referencing it in subsequent examples.

Dimension	Reasoning	Score
Conciseness	The body is lean — mostly executable code with brief intros and 'Key Patterns' bullets, with little concept over-explanation — but the @RequiredArgsConstructor/@Slf4j/@Transactional DI-and-logging pattern is repeated across several service examples (OrderProcessingService, DocumentService, ProcessingService), which could be tightened.	4 / 5
Actionability	Provides complete, copy-paste-ready Java classes, YAML config, and Maven POM snippets that cover the common Quarkus/Camel cases (REST resources, Panache repositories, services, Camel routes, caching, async, health checks, dependencies).	5 / 5
Workflow Clarity	The skill is a topical pattern catalog with a 'When to Activate' list and organized sections rather than a sequenced multi-step process; structure is present but there are no explicit validation checkpoints or feedback loops because no end-to-end workflow is presented.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the entire ~720-line reference is inlined in a single SKILL.md with no bundle files and no one-level-deep external references, so content that could live in separate reference files (e.g. Maven dependencies, Camel route catalog) is not split out.	3 / 5
	Total	15 / 20 Passed

Description

87%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, specific description that clearly states the capability domain and provides explicit, natural-language activation triggers. It is well-distinguished from other backend skills and answers both 'what' and 'when' concretely.

Dimension	Reasoning	Score
Specificity	Names the Quarkus domain plus several specific capability areas ('Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing'), but these are domain labels rather than concrete verb-noun actions, leaving minor gaps versus a fully action-verb enumeration.	4 / 5
Completeness	Explicitly answers both what ('Quarkus 3.x LTS architecture patterns with Camel...') and when ('Use for Java Quarkus backend work...', 'Use when building or reviewing a Quarkus service, especially with Camel messaging or Panache data access') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('building or reviewing a Quarkus service', 'Camel messaging', 'Panache data access', 'event-driven architectures'); good coverage though a few synonymous phrasings are absent and file extensions do not apply to a framework skill.	4 / 5
Distinctiveness Conflict Risk	The Quarkus + Camel + Panache + event-driven combination is a clear niche with distinctive triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (724 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/quarkus-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.