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.
35
3%
Does it follow best practices?
Impact
93%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/kafka-producer-consumer/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title with boilerplate metadata rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Kafka producers and consumers, configures topics, handles message serialization/deserialization, sets up consumer groups, and manages offset commits.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Kafka messaging, publishing/consuming messages, event streaming, topic configuration, consumer groups, or message brokers.'
Remove the duplicate trigger term ('kafka producer consumer' is listed twice) and expand with natural variations users would actually say, such as 'kafka setup', 'message queue', 'event-driven architecture', 'kafka config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Kafka Producer Consumer' but does not describe any concrete actions. There are no specific capabilities listed like 'create producers', 'configure consumers', 'handle message serialization', etc. It is essentially just a label. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and the 'when' clause is just a generic 'auto-activating skill for Backend Development' with no explicit trigger guidance. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'kafka producer consumer' repeated twice. Missing natural variations users would say like 'kafka messaging', 'publish messages', 'consume topics', 'kafka setup', 'message broker', 'event streaming', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Kafka is a fairly specific technology domain, so it has some inherent distinctiveness. However, the lack of specific actions means it could overlap with general messaging or event streaming skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual instructional content. It is entirely composed of meta-descriptions and trigger phrases, repeating 'kafka producer consumer' without ever providing any concrete guidance, code, configuration, or workflow for working with Kafka producers and consumers. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for Kafka producer and consumer implementations in at least one language (e.g., Python with confluent-kafka or Node.js with kafkajs), including connection setup, message production, and consumption.
Define a clear workflow with steps: configure broker connection → create producer/consumer → send/receive messages → handle errors → validate message delivery, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical content covering serialization, partitioning, consumer groups, and error handling patterns.
Add references to separate files for advanced topics like exactly-once semantics, schema registry integration, and performance tuning rather than leaving the skill content-free.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Kafka producers or consumers. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no configuration snippets, no specific Kafka producer/consumer patterns. It only describes what it could do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive block with no meaningful structure. Sections exist but contain no substantive content and there are no references to detailed materials or external files. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- Reviewed
Table of Contents
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.