CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/quarkus-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

The body delivers concrete, mostly executable Quarkus/Camel patterns with good topical organization, but it is a monolithic catalog: it mixes quick-reference patterns with file-level reference material (POM, logback.xml, application.yml), offers no sequenced workflow or validation checkpoints, and includes generic best-practice bullets Claude already knows.

Suggestions

Move the Maven dependency listing, logback.xml configuration, and full application.yml into reference files (e.g., references/dependencies.md, references/logging-config.md, references/configuration.md) and keep one-line pointers in SKILL.md.

Trim or cut the generic best-practice bullets (transactions, testing, dev-mode hot reload) that restate knowledge Claude already has, keeping only Quarkus/Camel-specific guidance.

Add a short sequenced workflow for standing up a new service (dependencies → YAML config profiles → Panache repository → Camel routes → health checks → tests) with an explicit validation or verification checkpoint.

DimensionReasoningScore

Conciseness

The code-heavy sections are dense and mostly earn their tokens, but generic best-practice bullets ('Keep transactions short and focused', 'Mock all external dependencies', 'Use Quarkus dev mode for hot reload') restate what Claude already knows, and the ~70-line Maven dependency listing is boilerplate that could be trimmed or referenced.

3 / 5

Actionability

Mostly executable, concrete examples — complete RouteBuilder configurations, Panache repository queries, exception mappers, and DTO validation — but undefined custom placeholders (CustomLog, SafeAutoCloseable, LogContext) and bean-method invocations leave minor gaps that keep it from copy-paste readiness.

4 / 5

Workflow Clarity

The body is a pattern catalog with a 'When to Activate' trigger list but no sequenced process (e.g., dependencies → config → routes → tests) and no validation checkpoints; testing guidance is advisory ('Test conditional flow logic thoroughly') with no concrete test code or verification steps.

3 / 5

Progressive Disclosure

Section headers are clear and well-organized, but all ~720 lines live in a single SKILL.md with no bundle files; reference material such as the full logback.xml, application.yml, and Maven POM sections is inlined where separate reference files would serve better.

3 / 5

Total

13

/

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 description: it names concrete technologies and capabilities, states both what the skill covers and when to use it in third person, and carves out a distinct niche. The only gap is a few missing natural trigger synonyms (RabbitMQ, Hibernate, RESTEasy).

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities — 'Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing' — that comprehensively cover the skill's scope without vague filler.

5 / 5

Completeness

It explicitly answers both what ('Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing') and when ('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

Natural terms like 'Quarkus', 'Camel', 'Panache', 'event-driven architectures', and 'building or reviewing a Quarkus service' are present, but common variations users would say such as 'RabbitMQ', 'Hibernate', or 'JAX-RS/RESTEasy' are missing.

4 / 5

Distinctiveness Conflict Risk

The Quarkus + Camel + Panache combination is a clear niche with distinct trigger terms, minimizing overlap risk with generic Java, Spring, or messaging skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.