CtrlK
BlogDocsLog inGet started
Tessl Logo

414-frameworks-quarkus-kafka

Use when you need Kafka messaging in Quarkus with SmallRye Reactive Messaging — including channel/topic design, build-time Jackson serialization, typed @Channel/@Incoming, ack/failure strategies, retries/DLQ, idempotency, Dev Services, and Testcontainers integration tests. This should trigger for requests such as Add Kafka in Quarkus; Review Reactive Messaging consumers; Improve failure handling for Quarkus Kafka; Configure Quarkus Reactive Messaging Kafka channels; Add Quarkus Kafka failure strategy or DLQ handling. Part of Plinth Toolkit

73

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, concise skill body with strong workflow validation (compile-before, stop-on-failure, verify-after) and clean one-level-deep progressive disclosure to a real reference file. Minor trimming and slightly more concrete implementation guidance would push conciseness and actionability to 5.

Suggestions

Trim the redundant opening line and consider folding the 'When to use this skill' bullet list into the (already rich) description to save tokens in the body.

Add one concrete snippet (e.g., a minimal @Incoming/@Channel example or an application.properties channel config) so the implementation step is executable without always opening the reference.

DimensionReasoningScore

Conciseness

Mostly lean and well-structured with no explanation of concepts Claude already knows; the opening line ('Apply Quarkus Kafka guidance with concrete examples for design, implementation, and error handling.') and the 'When to use this skill' list are slightly redundant with the title/description and could be trimmed.

4 / 5

Actionability

Provides concrete copy-paste commands ('./mvnw compile', 'mvn clean verify') and a specific reference path, but the core implementation step ('Implement/refactor channels, serializers, and failure strategies in Reactive Messaging') is high-level and defers detail to the reference.

4 / 5

Workflow Clarity

A clearly sequenced 4-step workflow with explicit validation checkpoints and feedback loops: MANDATORY compile-before, SAFETY stop-on-failure, and VERIFY-after, satisfying the destructive/batch feedback-loop requirement.

5 / 5

Progressive Disclosure

A concise overview with well-organized sections (Constraints, When to use, Workflow, Reference) pointing to a single, verified one-level-deep reference file (references/414-frameworks-quarkus-kafka.md exists), with clear navigation.

5 / 5

Total

18

/

20

Passed

Description

95%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, comprehensive description that clearly scopes the Quarkus/Kafka/SmallRye Reactive Messaging niche with concrete capabilities and explicit trigger phrases. The only issue is second-person voice ('you need') which costs one specificity point per the rubric's voice guideline.

Suggestions

Rewrite in third person to lift specificity to 5: e.g., 'Triggers for requests such as Add Kafka in Quarkus...' instead of 'Use when you need Kafka messaging...'.

DimensionReasoningScore

Specificity

Lists many concrete capabilities ('channel/topic design, build-time Jackson serialization, typed @Channel/@Incoming, ack/failure strategies, retries/DLQ, idempotency, Dev Services, and Testcontainers integration tests') which is comprehensive; penalized one point because the description uses second-person voice ('Use when you need...').

4 / 5

Completeness

Explicitly answers both what ('Kafka messaging in Quarkus with SmallRye Reactive Messaging — including...') and when ('Use when you need...', 'This should trigger for requests such as...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural request phrasings users would actually say ('Add Kafka in Quarkus', 'Review Reactive Messaging consumers', 'Improve failure handling for Quarkus Kafka', 'Configure Quarkus Reactive Messaging Kafka channels'), giving comprehensive coverage of the domain's natural terms.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Quarkus + Kafka + SmallRye Reactive Messaging) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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/plinth
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.