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.

68

Quality

81%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

This is a well-organized, comprehensive skill for a complex multi-phase workflow. Its strengths are the clear phased workflow, explicit categorization system, and well-signaled references to supporting documents. Its main weaknesses are the lack of executable code examples (Terraform snippets, actual grep commands, schema file examples), some content repetition, and the inability to verify referenced bundle files exist.

Suggestions

Add at least one concrete, executable Terraform resource example inline (e.g., a confluent_schema resource block) so the skill is actionable without relying entirely on the missing terraform-templates.md reference.

Include a concrete example of a generated schema file (e.g., a small Avro .avsc with PII tags) to make Phase 5 actionable rather than purely descriptive.

Remove the duplicate output directory structure listing—it appears both in Phase 5/6 descriptions and again in the 'Output Organization' section. Keep only the comprehensive final one.

DimensionReasoningScore

Conciseness

The skill is fairly well-structured and avoids explaining basic concepts Claude already knows (e.g., what Kafka is), but there is notable repetition—the output directory structure is shown twice, category definitions appear in multiple places, and some sections like 'CRITICAL' callouts could be tightened. The content is moderately efficient but could be leaner.

2 / 3

Actionability

The skill provides concrete directory structures, file naming conventions, category definitions, and specific grep patterns to look for, which is good. However, it lacks executable code examples—no actual Terraform snippets, no schema file examples, no grep commands. It references templates and patterns in external files that are not provided in the bundle, making the main skill incomplete on its own.

2 / 3

Workflow Clarity

The 8-phase workflow (Phase 0-7) is clearly sequenced with explicit steps within each phase. Validation checkpoints are present (e.g., 'Call schema_lint(path: schemas/, fix: true)', validate formatting requirements, category classification criteria). The migration rollout ordering provides clear sequencing by category with explicit ordering (producers first vs consumers first). Edge cases are addressed.

3 / 3

Progressive Disclosure

The skill has excellent structure with clear references to 6 separate reference documents (detection-patterns.md, schema-inference.md, categorization.md, terraform-templates.md, report-template.md, code-migration.md) that are one level deep and well-signaled. However, since no bundle files are provided, these references cannot be verified as existing, and the main SKILL.md contains substantial inline detail that partially duplicates what the references presumably cover (e.g., category definitions, rollout ordering). The inline content is borderline too much for an overview.

2 / 3

Total

9

/

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.

This is an excellent skill description that clearly articulates multiple concrete capabilities in a specific technical domain. It includes an explicit 'Use this skill when...' clause with natural trigger terms, and the combination of Kafka + Schema Registry + Terraform makes it highly distinctive. The description uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: scan for Kafka applications, extract schemas from data models, tag PII fields, generate Terraform for Confluent Schema Registry, and produce a migration report with rollout ordering.

3 / 3

Completeness

Clearly answers both 'what' (scan, extract schemas, tag PII, generate Terraform, produce migration report) and 'when' with an explicit 'Use this skill when...' clause listing specific trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Kafka', 'schemas', 'PII', 'Terraform', 'Confluent Schema Registry', 'producer/consumer configurations', 'migration report', 'analyze a folder or repo'. These cover the domain well with natural variations.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche combining Kafka, Schema Registry, Terraform generation, and PII tagging. Very unlikely to conflict with other skills due to the specific technology stack and workflow described.

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.

Validation11 / 11 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.