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
Quality
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 placeholder that provides almost no useful information for skill selection. It names the technology but fails to describe any concrete capabilities, lacks natural trigger terms users would actually say, and provides no guidance on when Claude should select this skill over others.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Kafka producer and consumer configurations, handles message serialization/deserialization, sets up topic subscriptions, and troubleshoots connection issues.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about publishing messages to Kafka, consuming from topics, configuring Kafka clients, or setting up event streaming.'
Include common variations users might say: 'message queue', 'event streaming', 'publish/subscribe', 'Kafka topics', 'message broker'.
| 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 and merely repeats the skill name. | 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 this covers (configuration, monitoring, code generation, troubleshooting) could cause overlap with other Kafka-related or general messaging 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 a placeholder template with zero actual content about Kafka producers or consumers. It contains only meta-descriptions of what a skill should do without any concrete implementation guidance, code examples, or technical information. The content adds no value beyond what Claude already knows about Kafka.
Suggestions
Add executable code examples for both Kafka producer and consumer implementations in at least one language (Node.js, Python, or Go)
Include concrete configuration examples with common settings (bootstrap servers, serializers, consumer groups, etc.)
Provide a clear workflow for setting up and testing Kafka producers/consumers with validation steps
Add specific patterns for error handling, retries, and message acknowledgment that are Kafka-specific
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical information. It explains what the skill does in abstract terms without providing any concrete Kafka producer/consumer code, configurations, or patterns that Claude doesn't already know. | 1 / 3 |
Actionability | No executable code, no specific commands, no concrete examples. The entire content describes rather than instructs - phrases like 'Provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating producers or consumers, no validation checkpoints, no error handling patterns - just meta-descriptions of what the skill claims to do. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate sections. No references to detailed documentation, no links to examples, no organization of Kafka concepts (producers vs consumers, configuration, error handling, etc.). | 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
994edc4
- 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.