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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A clean, well-structured overview with strong conciseness, a validated workflow, and proper one-level-deep progressive disclosure. Its main gap is actionability: the body gives concrete build commands but no executable messaging code or config, leaving the core implementation guidance abstract until the reference is opened.

Suggestions

Add one minimal executable snippet to the body — e.g. a basic @Incoming consumer method or an @Channel Emitter producer — so the skill is actionable without immediately opening the reference.

Include a small application.properties example showing a channel-to-topic mapping with failure-strategy=dead-letter-queue, since configuration is central to this skill.

Optionally inline a one-line ack/failure or retry snippet so the most common ask ('Add Quarkus Kafka failure strategy or DLQ handling') has a concrete starting point in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Lean body with no Concept-explaining filler: a one-line overview, terse constraint bullets with concrete commands, a short when-to-use list, four compact workflow steps, and a single reference link. Every token earns its place.	3 / 3
Actionability	The build commands ('./mvnw compile', 'mvn clean verify') are concrete and executable, but the core messaging guidance is abstract — 'Implement/refactor channels, serializers, and failure strategies in Reactive Messaging' describes rather than instructs, and the body contains no executable code or config snippets, deferring all detail to the reference.	2 / 3
Workflow Clarity	Clear four-step sequence with explicit validation checkpoints and a feedback loop: MANDATORY compile before changes, SAFETY stop-on-failure, and VERIFY (clean verify) after improvements.	3 / 3
Progressive Disclosure	Body is a concise overview that points one level deep to a single, real, well-signaled reference (references/414-frameworks-quarkus-kafka.md, verified to exist), referenced both in workflow step 1 and a dedicated Reference section.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 specific, well-triggered description with clear what/when coverage and a distinct Quarkus-Kafka niche. The only weakness is the second-person 'you need' phrasing in the trigger clause, which the rubric flags as a voice penalty.

Suggestions

Rephrase the opening to impersonal/third-person voice, e.g. 'Use when working with Kafka messaging in Quarkus...' or 'Use when the user needs Kafka messaging in Quarkus...', to avoid the second-person 'you need'.

Dimension	Reasoning	Score
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 would warrant a 3, but the trigger clause 'Use when you need Kafka messaging' uses second person ('you need'), which the rubric penalizes by reducing specificity by one.	2 / 3
Completeness	Explicitly answers both what (Kafka messaging capabilities enumerated) and when ('Use when you need Kafka messaging in Quarkus...' plus 'This should trigger for requests such as...'), matching the top anchor.	3 / 3
Trigger Term Quality	Strong natural trigger phrases users would actually say: 'Add Kafka in Quarkus', 'Review Reactive Messaging consumers', 'Improve failure handling for Quarkus Kafka', 'Configure Quarkus Reactive Messaging Kafka channels', and 'Add Quarkus Kafka failure strategy or DLQ handling'.	3 / 3
Distinctiveness Conflict Risk	Narrow niche — Quarkus + SmallRye Reactive Messaging + Kafka — with distinct, specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: aaee915

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.