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

85%

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

71%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.

The body is a well-structured, token-efficient overview that defers detail appropriately to one real reference file and includes compile/verify validation checkpoints. Its main weakness is that the middle workflow steps are directional rather than actionable, containing no concrete Micronaut Kafka examples or configuration in the body itself.

Suggestions

Add a minimal inline example in the body (e.g., a short @KafkaListener with errorStrategy, or the key application.yml properties) so the most common case is actionable without opening the reference.

Make workflow steps 2-3 concrete: specify what to inspect (application.yml consumer groups, errorStrategy settings, existing @KafkaClient interfaces) and what decisions map to which change.

Add a recovery loop for failed verification (fix and re-run ./mvnw clean verify) to complement the existing stop-on-failure SAFETY rule.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows, but the "When to use this skill" section restates the description's triggers verbatim and the reference file is pointed to three separate times.	4 / 5
Actionability	Concrete build commands are given ("./mvnw compile", "./mvnw clean verify"), but the core workflow steps are high-level directions — "Identify delivery guarantees and resilience requirements" and "Implement/refactor clients, listeners, and failure strategies" — with all concrete messaging guidance deferred to the reference file.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (MANDATORY compile before, SAFETY stop on failure, VERIFY after), but there is no fix-and-retry recovery loop or guidance for what to do when verification fails.	4 / 5
Progressive Disclosure	A ~40-line overview with a single existing reference (references/514-frameworks-micronaut-kafka.md) that is clearly signaled in both the workflow and a dedicated Reference section, exactly one level deep.	5 / 5
	Total	16 / 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 description: it states concrete capabilities in third person and provides an explicit trigger list of natural user requests, both what and when. The only gap is that a few natural synonym phrasings (consumers/producers, event messaging) are not included.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "@KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling" — giving comprehensive coverage of the Micronaut Kafka domain.	5 / 5
Completeness	Explicitly answers both what ("@KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy... retries and dead-letter processing") and when ("This should trigger for requests such as Add Kafka in Micronaut; Review Micronaut Kafka listeners...").	5 / 5
Trigger Term Quality	Natural user phrasings like "Add Kafka in Micronaut", "Review Micronaut Kafka listeners", and "Configure Micronaut Kafka clients listeners or SerDes" are present, but common synonyms such as "consumers/producers" or "event messaging" are only partially covered.	4 / 5
Distinctiveness Conflict Risk	Every capability and trigger phrase is scoped to "Micronaut Kafka", creating a clear niche with distinct triggers; only negligible overlap risk with sibling Plinth Toolkit 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: dca88dc

Reviewed: 3 hours 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.