kafka-stream-processor
Kafka Stream Processor - Auto-activating skill for Data Pipelines. Triggers on: kafka stream processor, kafka stream processor Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill kafka-stream-processorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a label rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The redundant trigger term and absence of a 'Use when...' clause make it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Processes streaming data from Kafka topics, transforms messages, handles consumer/producer configurations, and manages stream topologies.'
Include a 'Use when...' clause with natural trigger terms: 'Use when working with Kafka streams, real-time data processing, message queues, event-driven architectures, or streaming ETL pipelines.'
Add common user terminology variations: 'Kafka consumer', 'Kafka producer', 'streaming data', 'message broker', 'event streams', '.avro', '.json messages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the technology ('Kafka Stream Processor') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'processes', 'transforms', 'filters', or similar action words. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the technology, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('kafka stream processor' listed twice) and overly technical. Missing natural variations users might say like 'streaming data', 'message queue', 'event processing', 'Kafka consumer', 'Kafka producer', or 'real-time data'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Kafka' is a specific technology that provides some distinctiveness, the vague 'Data Pipelines' category and lack of specific use cases could cause overlap with other data processing or streaming skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It contains only generic placeholder text that describes what a Kafka stream processor skill might do without providing any actual guidance, code, configurations, or actionable information. The skill fails on every dimension because it teaches nothing.
Suggestions
Add executable code examples showing Kafka Streams topology setup, including KStream/KTable operations with actual Java or Python code
Include concrete configuration examples (application.id, bootstrap.servers, serdes) with production-ready values and explanations of critical settings
Define a clear workflow for building stream processors: 1) Define topology, 2) Configure serdes, 3) Handle errors/retries, 4) Test with TopologyTestDriver, 5) Deploy with validation
Add references to separate files for advanced patterns (windowing, joins, state stores) and common troubleshooting scenarios
| 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 no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific Kafka configurations, no actual stream processing patterns. The entire skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, configurations, or advanced topics. It's neither a useful overview nor does it point anywhere useful. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%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
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.