Help us improve
Share bugs, ideas, or general feedback.
From kafka-skills
Reviews Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count, and task health.
npx claudepluginhub lensesio/agentic-engineering-for-apache-kafka --plugin kafka-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/kafka-skills:kafka-connector-review [required: environment name] [optional: connector name to focus on][required: environment name] [optional: connector name to focus on]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reviews Kafka Connect connector configurations for common misconfigurations. Connectors are defined as JSON/YAML and are entirely language-agnostic.
Audits Kafka topic configurations against production best practices using the Lenses MCP server. Checks replication factor, retention, partitions, compaction, naming conventions, orphaned topics, and missing metadata.
Creates and validates Redpanda Connect YAML pipeline configurations from descriptions like Kafka to S3 or repairs broken configs using rpk scaffold and lint tools.
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.
Share bugs, ideas, or general feedback.
Reviews Kafka Connect connector configurations for common misconfigurations. Connectors are defined as JSON/YAML and are entirely language-agnostic.
Target environment: $ARGUMENTS
Copy this checklist and track your progress:
Connector Review Progress:
- [ ] Step 1: List all connectors
- [ ] Step 2: Inspect each connector's configuration
- [ ] Step 3: Validate configurations against plugin schemas
- [ ] Step 4: Audit for common misconfigurations
- [ ] Step 5: Generate report
Use the Lenses MCP list_kafka_connectors tool to get all connectors with:
Flag immediately:
Expected output: List of all connectors with name, class, status and task states.
Validation: If no connectors are returned, report that no Connect cluster is configured and stop.
Use the Lenses MCP get_kafka_connector_target_definition tool to get the full configuration YAML for each connector.
Use the Lenses MCP validate_connector_configuration tool to validate each connector's config against its plugin's schema. This catches:
errors.tolerance=all without errors.deadletterqueue.topic.name (silently drops messages)errors.tolerance (defaults to none, connector stops on any error)errors.log.enable=true (errors not logged)errors.deadletterqueue.context.headers.enable=true for richer DLQ metadatakey.converter or value.converter mismatch with topic serialisation formatorg.apache.kafka.connect.storage.StringConverter for structured data (should use Avro/JSON/Protobuf converter)schemas.enable setting where schemas are expectedtasks.max=1 on high-throughput connectors (limits parallelism)tasks.max should align with source partitioningtasks.max should align with topic partition countconsumer.override.* or producer.override.* for performance tuning{source/sink}-{system}-{entity})User says: "Review all connectors in staging"
Actions:
User says: "My sink connector is failing, can you check why?"
Actions:
User says: "Review the config for the elasticsearch-sink connector"
Actions:
Cause: No Kafka Connect cluster is configured in the environment or no connectors are deployed.
Solution: Verify that a Connect cluster exists via Lenses UI. Check get_deployment_targets for available Connect clusters.
Cause: The connector plugin class is not installed on the Connect cluster. Solution: Report the missing plugin. This is a deployment issue, not a configuration issue.
Cause: The connector framework is running but individual tasks have encountered errors. Solution: Check each task's status. Common causes include authentication failures, network issues or schema mismatches with the external system.
## Connector Review Report
### Environment: {name}
### Connector Status Overview
| Connector | Class | Status | Tasks | Failed Tasks |
|-----------|-------|--------|-------|-------------|
| name | class | RUNNING | 3/3 | 0 |
### Critical (must fix)
- [connector-name] Description of the issue
Current: {current config} | Recommended: {recommended config}
### Warning (should fix)
- [connector-name] Description of the issue
Current: {current config} | Recommended: {recommended config}
### Validation Errors
- [connector-name] {field}: {validation error message}
### Suggestion (consider improving)
- [connector-name] Description of the suggestion
Recommendation: {how to improve}
### Summary
- X connectors reviewed
- Y critical issues found
- Z warnings found
- Failed connectors: N
- Failed tasks: M