Covers the Neo4j Go Driver v6 — driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, and connection tuning. Use when writing Go code that connects to Neo4j, setting up NewDriver or ExecuteQuery, debugging sessions/transactions/result handling, or working with neo4j-go-driver v5→v6 migration. Triggers on NewDriver, ExecuteQuery, SessionConfig, ManagedTransaction, neo4j-go-driver. Does NOT handle Cypher query authoring — use neo4j-cypher-skill. Does NOT cover driver version migration steps — use neo4j-migration-skill.
94
92%
Does it follow best practices?
Impact
100%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Driver lifecycle and ExecuteQuery setup
v6 driver constructor
0%
100%
Single driver instance
100%
100%
VerifyConnectivity called
100%
100%
Driver closed on teardown
100%
100%
Env-var config
100%
100%
Database specified in query
100%
100%
Readers routing on read query
50%
100%
Parameterised query
100%
100%
Type-safe record extraction
100%
100%
Context timeout
100%
100%
v6 import path
0%
100%
Wrapped error returns
100%
100%
Bulk writes, streaming reads, and auto-commit queries
UNWIND batch pattern
100%
100%
Whole-slice parameter
100%
100%
Database name specified
100%
100%
Managed transaction for streaming
100%
100%
Lazy iteration
100%
100%
res.Err() checked
100%
100%
No side effects in callback
100%
100%
session.Run for CALL IN TRANSACTIONS
100%
100%
Session closed
100%
100%
Typed record extraction
25%
100%
Error wrapping
0%
100%
Explicit transactions and cross-session causal consistency
Explicit transaction used
100%
100%
Rollback on failure
100%
100%
Commit on success
100%
100%
Session closed in PlaceOrder
100%
100%
Database name in sessions
100%
100%
CombineBookmarks for causal consistency
100%
100%
GetRecordValue for typed extraction
100%
100%
SingleTWithContext for one-row query
100%
100%
Parameterised queries
100%
100%
Error wrapping
16%
100%
v6 import path
100%
100%
66ed0e1
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.