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. Part of cursor-rules-java project

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The skill is well-structured and concise with a solid safety-first workflow that includes compilation checks before and after changes. However, it lacks any concrete code examples for Kafka messaging patterns, deferring everything to a reference file. This makes the SKILL.md itself minimally actionable — a developer or Claude would need to read the reference before doing anything meaningful.

Suggestions

Add at least one concrete, executable code example inline (e.g., a minimal @Incoming channel consumer or application.properties Kafka configuration) so the skill is actionable without requiring the reference file.

Include a brief inline example of a failure/retry strategy or DLQ configuration, since these are highlighted as key use cases in the skill description.

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It doesn't explain what Kafka is, what Reactive Messaging does, or other concepts Claude already knows. Every section serves a clear purpose with no padding.	3 / 3
Actionability	The skill provides concrete commands (./mvnw compile, mvn clean verify) and a clear workflow, but lacks any executable code examples for the actual Kafka implementation patterns (channel configuration, serializer setup, failure strategies). All concrete guidance is deferred to the reference file.	2 / 3
Workflow Clarity	The workflow has a clear 4-step sequence with explicit validation checkpoints: compile before changes, stop on failure, verify after changes. The feedback loop (compile → stop if fails → apply → verify) is well-defined for a potentially destructive refactoring operation.	3 / 3
Progressive Disclosure	The skill correctly references a single detailed file (references/414-frameworks-quarkus-kafka.md) with one-level-deep navigation, but since no bundle files were provided, we cannot verify the reference exists or assess its quality. The SKILL.md itself is essentially a thin wrapper that defers almost all substantive content to the reference, making it overly dependent on that single file without providing any inline quick-start examples.	2 / 3
	Total	10 / 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.

This is a strong skill description that excels across all dimensions. It provides highly specific capabilities, natural trigger terms with example requests, explicit 'Use when' and 'This should trigger for' clauses, and a distinctive technology niche (Kafka + Quarkus + SmallRye). The only minor note is the 'Use when you need' phrasing uses second person, but the rest of the description avoids this pattern and the overall quality is high.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and capabilities: channel/topic design, build-time Jackson serialization, typed @Channel/@Incoming, ack/failure strategies, retries/DLQ, idempotency, Dev Services, and Testcontainers integration tests. These are highly specific technical capabilities.	3 / 3
Completeness	Clearly answers both 'what' (Kafka messaging in Quarkus with SmallRye Reactive Messaging, listing specific capabilities) and 'when' ('Use when you need...', 'This should trigger for requests such as...' with concrete examples). Has explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Kafka', 'Quarkus', 'Reactive Messaging', 'consumers', 'failure handling', 'DLQ', 'retries'. The explicit trigger examples ('Add Kafka in Quarkus', 'Review Reactive Messaging consumers', 'Improve failure handling for Quarkus Kafka') cover natural user phrasings well.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche combining Kafka + Quarkus + SmallRye Reactive Messaging. The specific technology stack combination and detailed feature list make it very unlikely to conflict with other skills. The trigger examples further narrow the scope.	3 / 3
	Total	12 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: dcf0eaa

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