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; Configure Micronaut Kafka clients listeners or SerDes; Add Micronaut Kafka retry or dead-letter handling. Part of Plinth Toolkit

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 concise, well-structured overview with strong validation gates and clean progressive disclosure via a real reference file. The main gap is actionability: the body delegates all Kafka-specific code and configuration to the reference rather than showing a concrete inline example.

Suggestions

Add one short inline Kafka example (e.g. a minimal @KafkaListener with errorStrategy) so the body gives concrete, copy-paste-ready guidance beyond the build commands.

Make step 3 of the Workflow more actionable by naming the specific error strategies or dead-letter pattern to apply instead of the generic 'Implement/refactor clients, listeners, and failure strategies'.

Reference the specific sections of the reference file (e.g. anchors or sub-headings) so Claude can jump straight to the relevant guidance rather than scanning the whole document.

Dimension	Reasoning	Score
Conciseness	A lean overview that delegates detail to the reference; no padding and no over-explanation of concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	Concrete build commands ('./mvnw compile', 'mvn clean verify') are present, but the core Kafka work is described abstractly ('Implement/refactor clients, listeners, and failure strategies') with no inline code or config; all specifics live in the referenced file.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints — compile before changes, stop on failure, verify after — forming a strong feedback loop for a build-affecting skill.	5 / 5
Progressive Disclosure	Clear overview with a single one-level-deep, well-signaled reference link to the verified references/514-frameworks-micronaut-kafka.md file; easy to navigate.	5 / 5
	Total	18 / 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, specific, and well-triggered description that clearly conveys both capability and usage context for a narrow Micronaut Kafka niche. Trigger phrasing is slightly repetitive but otherwise excellent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '@KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling' — giving comprehensive domain coverage.	5 / 5
Completeness	Explicitly answers both 'what' (the including clause enumerating capabilities) and 'when' ('Use when you need Kafka messaging in Micronaut' plus 'This should trigger for requests such as...').	5 / 5
Trigger Term Quality	Includes several natural trigger phrases ('Add Kafka in Micronaut; Review Micronaut Kafka listeners; Improve retry and failure handling for Micronaut Kafka') but they are somewhat repetitive and lack synonyms or file-extension variations.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to Kafka messaging in Micronaut with framework-specific annotations, creating a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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
Path: skills/514-frameworks-micronaut-kafka/SKILL.md
Commit: 05bf9d1

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.