What problem does it solve? Setting up bidirectional streaming between Kafka and Neo4j involves choosing among multiple sink strategies (Cypher, Pattern, CDC, CUD), configuring exactly-once semantics, dead-letter queues, schema registry converters, and native CDC cursor management, all of which are error-prone without a consolidated reference. ## Core Features & Use Cases - Sink Connector Strategies: Configure Cypher, Pattern, CDC, and CUD sink strategies with idempotent MERGE patterns, exactly-once semantics via offset tracking constraints, and DLQ error handling. - Source Connector & Native CDC: Stream Neo4j changes to Kafka using CDC-based or query-based source connectors, or consume change events in-process with db.cdc.query cursor-loop patterns in Python and Java. - Use Case: A team needs to mirror Kafka user events into a Neo4j graph with exactly-once delivery and route failed messages to a dead-letter queue; the skill provides the complete production connector configuration including the required NODE KEY constraint. ## Quick Start Ask the assistant to generate a Neo4j Kafka sink connector configuration that consumes a JSON topic and upserts Person nodes with exactly-once semantics and a dead-letter queue.