CtrlK
BlogDocsLog inGet started
Tessl Logo

kafka-schema-registry

Scan a project to identify Kafka applications, extract schemas from data models, tag PII fields, generate Terraform for Confluent Schema Registry registration, and produce a migration report with rollout ordering. Use this skill when a user asks to analyze a folder or repo for Kafka usage, extract schemas, audit producer/consumer configurations, or generate Terraform for Schema Registry.

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured, actionable skill body that sequences a multi-phase workflow and pushes detail into verified reference files. Strongest on progressive disclosure and actionability; minor conciseness and validation-feedback-loop improvements remain.

Suggestions

Deduplicate the terraform file-structure block (it appears in both Phase 6 and the Output Organization section) to tighten conciseness.

Replace the conditional Phase 5 validation ("if available") with a mandatory validation step plus an explicit fix-and-retry loop, since Terraform generation is a batch operation that warrants a feedback checkpoint.

Add an explicit "verify Terraform" checkpoint (e.g., terraform validate/plan) before declaring deliverables complete to strengthen the workflow's terminal validation.

DimensionReasoningScore

Conciseness

The body is efficient — concrete grep targets, directory trees, and YAML structures assume Claude's competence with minimal concept re-explanation — but contains minor repetition (e.g., the MANDATORY terraform file structure appears twice) that could be trimmed.

4 / 5

Actionability

Provides executable guidance: specific grep patterns (KafkaTemplate, producer.send), a concrete app-catalog YAML schema, naming conventions, and a file layout, with bulk templates offloaded to references; the inline guidance is concrete but template details live in referenced files.

4 / 5

Workflow Clarity

Seven numbered phases give a clear sequence with a validation checkpoint in Phase 5 ("Validate: Call schema_lint if available") and explicit categorization rules, but validation is conditional and lacks an explicit fix-retry feedback loop for the batch generation work.

4 / 5

Progressive Disclosure

Clear overview with one-level-deep references; all six referenced files (detection-patterns, schema-inference, categorization, terraform-templates, report-template, code-migration) exist and their fragment anchors resolve, with bulk content appropriately split into references.

5 / 5

Total

17

/

20

Passed

Description

92%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, specific description that clearly states multiple concrete capabilities and provides explicit "Use when" trigger guidance covering the main user intents. Only minor room to broaden trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "identify Kafka applications", "extract schemas from data models", "tag PII fields", "generate Terraform for Confluent Schema Registry registration", "produce a migration report with rollout ordering" — giving comprehensive coverage rather than generic language.

5 / 5

Completeness

Explicitly answers both what (concrete actions listed) and when ("Use this skill when a user asks to analyze...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases ("analyze a folder or repo for Kafka usage", "extract schemas", "audit producer/consumer configurations", "generate Terraform for Schema Registry") match what users would say, but a few common synonyms/extensions are absent, keeping it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Kafka + Confluent Schema Registry) with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

20

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.

Repository
confluentinc/agent-skills
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.