Neo4j Java Driver v6 — driver lifecycle, Maven/Gradle setup, executableQuery, executeRead/Write managed transactions, explicit transactions, async/reactive patterns, error handling, data type mapping, connection pool tuning, causal consistency/bookmarks. Use when writing Java or Kotlin code that connects to Neo4j via GraphDatabase.driver, executableQuery, SessionConfig, executeRead, executeWrite, or TransactionCallback. Does NOT handle Cypher authoring — use neo4j-cypher-skill. Does NOT cover driver version upgrades — use neo4j-migration-skill. Does NOT cover Spring Data Neo4j (@Node, Neo4jRepository) — use neo4j-spring-data-skill.
87
93%
Does it follow best practices?
Impact
100%
1.21xAverage score across 2 eval scenarios
Passed
No findings from the security scan
Neo4j Java driver setup with CRUD operations
Correct driver version
100%
100%
Correct Maven group/artifact
100%
100%
Env-var credentials
100%
100%
Single driver instance
100%
100%
AutoCloseable or try-with-resources
100%
100%
verifyConnectivity call
100%
100%
executableQuery API
0%
100%
Database name specified
0%
100%
RoutingControl.READ for reads
0%
100%
Parameterised Cypher
100%
100%
Neo4j bulk person import with null-safe result handling
Try-with-resources session
100%
100%
UNWIND batch write
100%
100%
MERGE not CREATE
100%
100%
Plain map conversion
70%
100%
Result consumed inside callback
70%
100%
Single executeWrite call
100%
100%
Null-safe city access
100%
100%
Record mapping
100%
100%
No side effects in callback
100%
100%
Environment variable config
100%
100%
a3627d2
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.