CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kafka-development

Best practices for Apache Kafka event streaming and distributed messaging. Use when building event-driven architectures, implementing producer/consumer patterns, designing topic partitioning strategies, setting up Kafka Streams, configuring schema registries, or integrating change data capture pipelines.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./kafka-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

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

The content delivers solid, actionable Kafka guidance anchored by two executable Java examples, but it is padded with Kafka 101 concept explanations Claude already knows and crams a broad domain into a single file with no progressive disclosure. Trimming the primer material and splitting specialized sections into reference files would substantially improve token efficiency.

Suggestions

Cut the 'Core Principles', 'Architecture Overview' (Core Components / Key Concepts), and basic definitions like 'Consumer lag = last produced offset - last committed offset' — Claude already knows Kafka fundamentals; keep only non-obvious guidance such as retry/redrive math and static membership settings.

Split specialized sections (Kafka Streams, Security, Testing, Common Patterns) into references/ files (e.g., references/streams.md, references/security.md) and keep SKILL.md as a concise overview with one-level-deep pointers, rather than a ~320-line monolith.

Remove the stray line 'Leave NO todos, placeholders, or missing pieces in the implementation' — it is an implementation-instruction leak unrelated to Kafka best practices and adds confusion without guidance value.

DimensionReasoningScore

Conciseness

The body spends significant space explaining Kafka concepts Claude already knows: 'Topics: Categories/feeds for organizing messages', 'Producers: Clients that publish messages to topics', 'Messages are appended to partitions in order', 'Each message has an offset - a unique sequential ID within the partition', and 'Consumer lag = last produced offset - last committed offset'. The Core Principles and Architecture Overview sections are pure Kafka primer material, and the stray line 'Leave NO todos, placeholders, or missing pieces in the implementation' is irrelevant padding — this matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor. It is not a 1 because the producer/consumer sections do carry non-obvious configuration guidance.

2 / 5

Actionability

Two complete, executable Java examples (producer with idempotence and callback error handling; consumer with manual commit and DLT routing) plus concrete settings throughout ('acks=all', 'enable.auto.commit=false', 'group.instance.id', 'min.insync.replicas', compression options). Not a 5 because several sections give only abstract direction — the Common Patterns (event sourcing, CQRS, saga) and Kafka Streams sections describe ideas without any executable code, commands, or concrete configuration values.

4 / 5

Workflow Clarity

The 7-step 'Setting Up a Kafka Producer-Consumer Pipeline' workflow is clearly sequenced and includes an explicit verification checkpoint ('Test end-to-end — use Testcontainers or an embedded Kafka broker to verify the full produce-consume-commit cycle, including failure and rebalance scenarios'). Not a 5 because there are no feedback loops for what to do when a checkpoint fails, and the rest of the document abandons the workflow structure for reference material.

4 / 5

Progressive Disclosure

The body has clear section headers with reasonable in-file navigation, but it is a ~320-line monolith with no bundle files at all — content that clearly belongs in separate references (Kafka Streams, Security, Testing, Common Patterns) is inlined in SKILL.md. This fits the 'some structure, but content that should be separate is inline' anchor; it is above a 2 because the headers do provide organized navigation.

3 / 5

Total

13

/

20

Passed

Description

87%Weight 40%Scale 1-5

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, well-scoped description with explicit what/when structure and concrete Kafka-specific trigger phrases. The only weakness is that capabilities are expressed through the 'Use when' clause rather than direct action verbs, leaving the 'what' as the slightly generic 'Best practices for'.

DimensionReasoningScore

Specificity

The description names the domain ('Apache Kafka event streaming and distributed messaging') and lists several specific capability areas ('producer/consumer patterns', 'topic partitioning strategies', 'Kafka Streams', 'schema registries', 'change data capture pipelines'). It falls short of the 5 anchor because the 'what' is the generic phrase 'Best practices for' rather than concrete action verbs, and a few capability areas (monitoring, security, consumer groups) go unmentioned.

4 / 5

Completeness

Clearly answers 'what' ('Best practices for Apache Kafka event streaming and distributed messaging') and 'when' with an explicit 'Use when' clause enumerating six concrete trigger scenarios. This matches the anchor for explicitly answering both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms users would say: 'Kafka', 'event-driven architectures', 'producer/consumer', 'partitioning', 'Kafka Streams', 'schema registries', 'change data capture'. A few common variations are missing ('CDC' as an acronym, 'topics', 'consumer groups', 'offsets'), so it fits the 'good coverage, a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The skill is tightly scoped to Apache Kafka with Kafka-specific triggers (Kafka Streams, schema registries, CDC pipelines), giving it a clear niche with minimal overlap risk against other skills. Not the 4 anchor because the triggers are unambiguously Kafka-domain rather than merely 'mostly distinct'.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Mindrally/skills

Path

kafka-development/SKILL.md

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.