kafka-producer-consumer

Kafka Producer Consumer - Auto-activating skill for Backend Development. Triggers on: kafka producer consumer, kafka producer consumer Part of the Backend Development skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill kafka-producer-consumer

What are skills?

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs, uses redundant and limited trigger terms, and lacks any explicit guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple options.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates Kafka producers and consumers, configures serialization/deserialization, handles message acknowledgment, and sets up topic subscriptions.'

Add a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to send or receive messages from Kafka, set up event streaming, or configure message brokers.'

Expand trigger terms to include natural variations users would say: 'message queue', 'event streaming', 'publish/subscribe', 'Kafka topics', 'message broker', 'consume messages'.

Dimension	Reasoning	Score
Specificity	The description only names the technology domain 'Kafka Producer Consumer' without describing any concrete actions. There are no verbs indicating what the skill actually does (e.g., 'creates producers', 'configures consumers', 'handles message serialization').	1 / 3
Completeness	The description fails to answer 'what does this do' beyond naming the technology, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause with meaningful context.	1 / 3
Trigger Term Quality	The trigger terms are redundant ('kafka producer consumer' listed twice) and overly technical. Missing natural variations users might say like 'message queue', 'publish messages', 'consume events', 'Kafka setup', or 'streaming data'.	1 / 3
Distinctiveness Conflict Risk	While 'Kafka' is a specific technology that provides some distinctiveness, the lack of detail about what aspects of Kafka it handles could cause conflicts with other potential Kafka-related skills (e.g., Kafka Streams, Kafka Connect, Kafka admin operations).	2 / 3
	Total	5 / 12 Passed

Implementation

This skill is an empty template with no actual content about Kafka producers or consumers. It contains only generic boilerplate describing what a skill should do without providing any concrete guidance, code examples, or actionable instructions for working with Kafka messaging.

Suggestions

Add executable code examples for both Kafka producer and consumer implementations in at least one language (Node.js, Python, or Go)

Include specific configuration examples (bootstrap servers, serializers, consumer groups, topics) with actual values or clear placeholders

Define a clear workflow for setting up Kafka messaging: connection setup -> producer creation -> message sending -> consumer setup -> message handling -> error handling

Add validation steps and common error scenarios (connection failures, serialization errors, offset management issues) with recovery guidance

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information.	1 / 3
Actionability	No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually implement a Kafka producer or consumer. Zero executable content.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content merely lists vague capabilities without explaining any process for Kafka producer/consumer implementation.	1 / 3
Progressive Disclosure	No structure beyond generic headings. No references to detailed documentation, no examples, no links to related materials. The content is a shallow placeholder with no depth or navigation.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Reviewed

22 days ago

Table of Contents

Activation 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.