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

—

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.

The SKILL.md body is well-structured: concise, with an explicit compile/verify validation workflow and clean progressive disclosure to a single real reference. Its only weakness is actionability — the concrete Kafka code and design detail is delegated to the reference rather than appearing inline, so the body alone is more procedural wrapper than copy-paste-ready guidance.

Suggestions

Add one short inline good/bad code snippet (e.g. a minimal @KafkaClient/@KafkaListener pair or the errorStrategy + DLQ handler) so the body is directly actionable without opening the reference.

Show the key errorStrategy configuration value inline (RETRY_EXPONENTIALLY_ON_ERROR with retryCount) since retries/dead-letter handling are named in the description as a core trigger.

Include the exact verify command target (e.g. which *IT classes Failsafe runs) inline so the VERIFY step is unambiguous without consulting the reference.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview that assumes Claude's competence, defers detail to the reference, and contains no concept-explaining padding; every section earns its place.	3 / 3
Actionability	It gives concrete executable commands (./mvnw compile, mvn clean verify) and a specific reference file to read, but the substantive Kafka implementation guidance lives one level deep in the reference rather than as inline copy-paste-ready examples, so it is not fully actionable on its own.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation checkpoints (MANDATORY compile-before, SAFETY stop-on-failure, VERIFY-after), forming a validate-fix feedback loop that the rubric rewards.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep, real bundle file (references/514-frameworks-micronaut-kafka.md) that is referenced and linked twice, giving clear navigation with no nested reference chain.	3 / 3
	Total	11 / 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.

The description is strong: it is specific, uses third-person imperative voice with no fluff, names explicit trigger phrases a user would naturally say, and clearly delineates a Micronaut+Kafka niche. It fully answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities (@KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, error handling), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (the capability list after 'including') and 'when' (an explicit 'Use when…' clause plus 'This should trigger for requests such as…'), satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Provides natural user phrasings across several verbs (Add Kafka in Micronaut; Review Micronaut Kafka listeners; Improve retry and failure handling; Configure clients listeners or SerDes; Add retry or dead-letter handling), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to Kafka messaging in Micronaut with framework-specific annotations (@KafkaClient, @KafkaListener, @Serdeable, TestPropertyProvider), a clear niche unlikely to conflict with generic Kafka or other-framework skills.	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 — 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.