314-frameworks-spring-kafka

Use when you need to design or implement Kafka messaging in Spring Boot — including topic design, producer/consumer implementation, JSON serialization with Boot factory customizers, Testcontainers `@ServiceConnection` integration tests, retries and dead-letter topics, idempotency, and error handling. This should trigger for requests such as Add Kafka in Spring Boot; Review Spring Kafka consumers; Improve retries and DLT in Spring Kafka; Configure Spring Kafka topics serializers or listener containers; Add Spring Kafka dead-letter topic handling. Part of Plinth Toolkit

Quality

96%

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

92%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 an efficient, well-structured overview that defers detail to a single real reference file and enforces compile/verify checkpoints around risky refactors. Its only gap is that the in-body apply step carries no executable code, relying entirely on the reference.

Suggestions

Add one minimal inline producer or consumer snippet so the apply step is actionable without first opening the reference.

State the expected verification outcome (e.g. test count or build success signal) so the report step has an explicit pass/fail criterion.

Name the specific reference sections to read per workflow step (e.g. 'see Example 5 for DLT') to sharpen navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line intro, a concise constraints block, a short when-to-use list, and a numbered workflow, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides concrete, runnable verification commands (./mvnw compile, mvn clean verify) and an explicit workflow, but the apply step defers all code examples to the reference file, leaving the in-body guidance high-level.	4 / 5
Workflow Clarity	Four-step sequence with explicit validation checkpoints (MANDATORY compile before, SAFETY stop on failure, VERIFY after) and a feedback loop, matching the top anchor for batch/refactor operations.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview that points to a single well-organized one-level-deep reference (references/314-frameworks-spring-kafka.md), which exists and contains the detailed examples; navigation is clearly signaled in both Constraints and Reference sections.	5 / 5
	Total	19 / 20 Passed

Description

100%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 description that clearly states what the skill does and when it should trigger, with natural user phrasings and minimal overlap risk. It is comprehensive without being padded.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — topic design, producer/consumer implementation, JSON serialization via Boot factory customizers, Testcontainers @ServiceConnection tests, retries/DLT, idempotency, error handling — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what the skill does and when to use it, with a clear "Use when you need to..." clause plus concrete trigger examples, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrasings ("Add Kafka in Spring Boot", "Review Spring Kafka consumers", "Improve retries and DLT", "Configure Spring Kafka topics serializers or listener containers") covering common variations a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to Spring Boot + Kafka messaging with niche-specific triggers, making it unlikely to fire for unrelated skills.	5 / 5
	Total	20 / 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/314-frameworks-spring-kafka/SKILL.md
Commit: 77b8825

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