514-frameworks-micronaut-kafka
Use when you need Kafka messaging in Micronaut — including @KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling. This should trigger for requests such as Add Kafka in Micronaut; Review Micronaut Kafka listeners; Improve retry and failure handling for Micronaut Kafka. Part of cursor-rules-java project
59
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/514-frameworks-micronaut-kafka/SKILL.mdQuality
Discovery
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 an excellent skill description that clearly defines its scope at the intersection of Kafka and Micronaut, lists specific concrete capabilities, provides explicit trigger guidance with example phrases, and occupies a distinct niche. The description is well-structured with a 'Use when' clause, detailed capability list, and example trigger requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions and concepts: @KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling. These are highly specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Kafka messaging in Micronaut with specific capabilities listed) and 'when' (explicit 'Use when' clause at the start, plus 'This should trigger for requests such as...' with concrete examples). Both dimensions are thoroughly covered. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Kafka', 'Micronaut', 'Kafka listeners', 'retry', 'failure handling', 'dead-letter', 'KafkaClient', 'KafkaListener'. The example trigger phrases ('Add Kafka in Micronaut', 'Review Micronaut Kafka listeners') further reinforce natural language matching. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Kafka' + 'Micronaut' creates a very specific niche. The description is unlikely to conflict with general Java skills, general Kafka skills, or general Micronaut skills because it targets the intersection of Kafka messaging within the Micronaut framework specifically. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a thin wrapper around a reference file, providing almost no standalone actionable content. The workflow is logically structured but too abstract to be useful without the reference. The skill would benefit significantly from including at least one concrete code example (e.g., a basic @KafkaClient/@KafkaListener pair) and more specific validation steps.
Suggestions
Add at least one concrete, executable code example in the skill body — e.g., a minimal @KafkaClient producer and @KafkaListener consumer with @Serdeable, so the skill is actionable even before reading the reference.
Make workflow steps more specific: replace 'Apply framework-aligned changes' with concrete sub-steps like 'Add @KafkaClient interface with @Topic annotation' or 'Configure dead-letter topic with @KafkaListener errorStrategy'.
Add a validation/feedback loop step: after 'Run verification', include explicit guidance on what to check if tests fail (e.g., serialization errors, topic configuration mismatches) and how to recover.
Include a brief quick-start section with a concrete example that demonstrates the most common use case (e.g., sending and receiving a message) so the skill provides immediate value without requiring the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary filler. The 'When to use this skill' section repeats what the frontmatter description already covers, and the workflow steps are somewhat generic. The constraints section is reasonably tight but could be more concise. | 2 / 3 |
Actionability | No concrete code examples, no specific Kafka annotations, no executable commands beyond generic Maven compile/verify. All substantive guidance is deferred to the reference file. The skill body itself provides only vague direction like 'Implement/refactor clients, listeners, and failure strategies.' | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence with compilation checks before and after changes, which is good. However, the steps themselves are vague ('Gather scope and decide target improvements', 'Apply framework-aligned changes') and lack specific validation checkpoints or error recovery loops beyond 'stop immediately if compilation fails.' | 2 / 3 |
Progressive Disclosure | There is a clear reference to a single detailed file, which is good one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself contains almost no substantive quick-start content — it's essentially just a pointer to the reference file with a generic workflow wrapper. | 2 / 3 |
Total | 7 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
0e10f84
- 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.