CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/kafka-consumer-tests

Tests Apache Kafka consumer and producer logic across KafkaJS (Node.js), kafka-go (Go), and Spring Kafka (Java) - spins up a real broker via the Testcontainers Kafka module, asserts offset management and consumer-group rebalance behavior, distinguishes at-least-once from exactly-once (EOS / transactions), validates idempotent producer configuration, and routes unprocessable messages to a dead-letter topic. Use when the user works with Kafka producers or consumers in any language and needs integration or unit tests that exercise delivery semantics, offset commits, rebalance handling, or dead-letter routing.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable testing skill with executable multi-language recipes, a clear step sequence, and appropriate one-level-deep reference splitting. The only weakness is mild verbosity in the overview and citation prose.

Suggestions

Trim the Overview's cross-broker comparison ('unlike SQS visibility-timeout, RabbitMQ ack/nack, or BullMQ job-state') to a single clause — the delivery-primitive point lands without enumerating every sibling broker.

Consolidate the repeated inline doc citations (e.g. '[kjs-consuming]' is referenced and re-linked in Steps 3, 4, and 5); define each once and refer back by short name to cut repeated prose.

Move the Python Testcontainers snippet (Step 1) — which has no later consumer/producer recipe — into references/other-language-recipes.md alongside the Java and Go recipes, keeping the main file focused on the KafkaJS core.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific with no basic-concept padding, but the overview framing ('unlike SQS visibility-timeout, RabbitMQ ack/nack, or BullMQ job-state') and some repeated per-document citation prose could be tightened without losing clarity.

2 / 3

Actionability

Every step supplies fully executable, copy-paste-ready code in TypeScript, Java, Go, Python, and YAML — e.g. the KafkaJS producer send, manual-commit consumer, and EOS transaction examples are complete and runnable.

3 / 3

Workflow Clarity

Steps 1–9 are clearly sequenced, each is a self-verifying test with explicit assertions (e.g. expect(received).toContain('post-rebalance')), and the Anti-patterns and Limitations sections act as checklists for fragile cases.

3 / 3

Progressive Disclosure

Core KafkaJS recipes live inline while Java and Go recipes are split into the one-level-deep references/other-language-recipes.md, clearly signaled in Step 8 and the References section, with the bundle file confirmed present.

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.

A strong, third-person description that states concrete capabilities and gives an explicit 'Use when...' trigger with natural keywords. It is specific, complete, and clearly distinct from sibling broker-testing skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'asserts offset management and consumer-group rebalance behavior, distinguishes at-least-once from exactly-once (EOS / transactions), validates idempotent producer configuration, and routes unprocessable messages to a dead-letter topic' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (the testing capabilities) and when via a 'Use when the user works with Kafka producers or consumers... and needs integration or unit tests that exercise delivery semantics...' clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say — 'Kafka producers or consumers', 'delivery semantics', 'offset commits', 'rebalance handling', 'dead-letter routing', 'integration or unit tests'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Kafka-testing niche across named libraries (KafkaJS, kafka-go, Spring Kafka) and is unlikely to trigger for the sibling sqs-tests / rabbitmq-tests / bullmq-tests skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents