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

—

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 body is a lean, well-structured overview with an explicit, validated workflow and a properly signaled single-level reference. Its only weakness is actionability: concrete Kafka implementation examples live entirely in the reference rather than the body.

Suggestions

Add one minimal in-body producer/consumer or topic-config snippet so the skill is actionable without opening the reference — e.g. a compact @KafkaListener example or NewTopic bean.

Optionally fold the duplicated 'When to use' trigger list (which echoes the description) into a single pointer, since the frontmatter description already carries those triggers.

Consider naming the specific reference sections relevant to each workflow step (e.g. 'retries/DLT rules') so Claude can jump to detail rather than scanning the whole reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what Kafka or Spring Boot is, and every section earns its place with concrete build commands and a tight workflow, matching the lean/efficient anchor rather than the mostly-efficient-but-could-be-tightened level (2).	3 / 3
Actionability	It gives concrete executable commands ('./mvnw compile', 'mvn clean verify') but the core messaging work is abstract — 'Implement/refactor Spring Kafka configuration, producer/consumer logic, and failure handling' with no in-body code or config examples, deferring all detail to the reference — fitting the some-guidance-but-incomplete anchor; not level 3 (no copy-paste Kafka examples) nor level 1 (concrete commands and clear steps are present).	2 / 3
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints — MANDATORY compile-before, SAFETY stop-on-failure, VERIFY after — plus a feedback loop (compile fails -> stop immediately), matching the explicit-validation anchor rather than the checkpoints-implicit level (2).	3 / 3
Progressive Disclosure	The body is a concise overview with a single, well-signaled one-level-deep reference ([references/314-frameworks-spring-kafka.md](references/314-frameworks-spring-kafka.md), a real 533-line file) referenced twice, keeping detail out of the main file and matching the clear-overview anchor; not level 2 since the reference is clearly signaled and only one level deep.	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 specific, trigger-rich, and complete, clearly answering both what the skill does and when to use it with natural user phrasing. It is narrowly scoped to Spring Boot Kafka messaging, keeping conflict risk low.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'topic design, producer/consumer implementation, JSON serialization with Boot factory customizers, Testcontainers `@ServiceConnection` integration tests, retries and dead-letter topics, idempotency, and error handling' — matching the multiple-specific-actions anchor, not merely naming the domain (level 2).	3 / 3
Completeness	Explicitly answers both what ('design or implement Kafka messaging in Spring Boot — including...') and when ('Use when you need...', 'This should trigger for requests such as...'), meeting the explicit-triggers anchor; not level 2 where 'when' is only implied.	3 / 3
Trigger Term Quality	Natural user phrasing is well covered — 'Add Kafka in Spring Boot', 'Review Spring Kafka consumers', 'Improve retries and DLT in Spring Kafka', 'Configure Spring Kafka topics serializers or listener containers' — terms a user would actually say, exceeding the some-keywords-missing-variations level (2).	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to 'Kafka messaging in Spring Boot' with distinct triggers unlikely to fire for other skills, matching the clear-niche anchor rather than the overlapping level 2.	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.