What problem does it solve? Streaming data between Apache Kafka and Neo4j requires choosing the right connector strategy, writing correct configuration, and handling delivery guarantees and errors — a process with many version-specific pitfalls. This Skill provides decision tables, complete configuration examples, and troubleshooting guidance for the Neo4j Connector for Kafka and the native Neo4j CDC API. ## Core Features & Use Cases - Sink connector strategies: Configure Cypher, Pattern, CDC, and CUD sink strategies with idempotent MERGE patterns, exactly-once semantics, and dead-letter queue error handling. - Source connector strategies: Stream Neo4j changes to Kafka via CDC-based source (Neo4j 5.13+) or query-based source for any edition. - Native CDC API: Query change events directly with db.cdc.query using selector filters and cursor-loop patterns in Python and Java, without Kafka. - Use Case: Mirror Kafka events into a Neo4j graph in production by generating a complete sink connector config with EOS offset tracking, DLQ routing, and schema registry converters. ## Quick Start Ask the assistant to generate a Neo4j Kafka sink connector configuration that consumes a Kafka topic and merges Person nodes with exactly-once semantics and a dead-letter queue.