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.

Quality

68%

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

Fix and improve this skill with Tessl

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

Quality

Content

37%

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

The skill is highly actionable with complete executable examples, but it is far from token-efficient: a large monolithic code dump with no progressive disclosure or file splitting, and no sequenced workflow with validation checkpoints. It would benefit from being trimmed to patterns and offloading reference material to bundle files.

Suggestions

Split heavy reference material (Maven dependencies, logback.xml, full application.yml) into files under references/ and link to them one level deep, leaving SKILL.md as a lean overview of patterns.

Add a sequenced workflow (e.g. resource -> service -> repository -> event publishing -> test) with explicit validation checkpoints for destructive or batch operations like native compilation and message publishing.

Trim boilerplate that Claude already knows (basic CDI/Panache mechanics) and reduce duplicated code blocks to minimal illustrative snippets to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is a ~720-line dump of fully-worked code across many concerns with minimal prose, repeating boilerplate Claude already knows rather than pointing to references; it does not assume Claude's competence.	1 / 3
Actionability	Provides numerous complete, executable Java/YAML/XML snippets (services, routes, repositories, config, health checks, dependencies) that are copy-paste ready.	3 / 3
Workflow Clarity	Sections are thematically organized, but there is no sequenced end-to-end workflow with validation checkpoints for risky batch/deploy operations; the "When to Activate" list is unordered and validation is only shown in code, not as steps.	2 / 3
Progressive Disclosure	A monolithic single-file wall of code with no bundle references and no navigation/signaling to deeper material; content that should be split (e.g. full Maven deps, logback config) is inlined.	1 / 3
	Total	7 / 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.

The description is concrete, third-person, and pairs clear capabilities with an explicit Use-for trigger, covering both what and when. It is well-scoped to the Quarkus/Camel backend niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ("Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing") rather than vague actions.	3 / 3
Completeness	Answers both "what" (architecture patterns with the listed capabilities) and "when" via the explicit "Use for Java Quarkus backend work with event-driven architectures" trigger.	3 / 3
Trigger Term Quality	Natural terms a user would say ("Java Quarkus backend", "event-driven architectures", "RESTful API") appear, with good coverage of the skill's domain vocabulary.	3 / 3
Distinctiveness Conflict Risk	The Quarkus+Camel+event-driven niche is specific and unlikely to collide with general Java or backend skills.	3 / 3
	Total	12 / 12 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: 754b8dd

Reviewed: 2 days 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.