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.
93
92%
Does it follow best practices?
Impact
95%
1.63xAverage score across 3 eval scenarios
Passed
No known issues
Repository pattern with driver lifecycle and Aura config
v6 import path
0%
100%
NewDriver not deprecated name
0%
100%
Aura URI scheme
75%
87%
Env-var configuration
62%
100%
VerifyConnectivity called
100%
100%
Driver Close deferred
100%
100%
Repository pattern
50%
100%
DatabaseName always set
0%
100%
ReadersRouting on reads
25%
100%
Parameterised queries
100%
100%
Typed record extraction
0%
100%
Context with timeout
100%
0%
Session closed
100%
100%
Batch UNWIND import vs per-record transactions
v6 import path
0%
100%
NewDriver not deprecated
100%
100%
UNWIND batch write
100%
100%
No per-record transactions
100%
100%
Parameterised queries
100%
100%
DatabaseName specified
0%
100%
VerifyConnectivity called
100%
100%
Driver Close deferred
100%
100%
Context with timeout
0%
100%
Counters from summary
0%
100%
Env-var credentials
71%
100%
Streaming queries, spatial Points, and structured error handling
Streaming API for large results
100%
100%
Lazy iteration with res.Err() check
100%
100%
ReadersRouting on read query
100%
100%
Spatial Point2D with correct SRID
0%
100%
Point passed as parameter
50%
100%
DatabaseName specified
0%
100%
Typed record extraction
0%
100%
Neo4jError handling
50%
100%
ConnectivityError handling
100%
100%
Context with timeout
0%
0%
Session closed
100%
100%
6d44d31
Table of Contents
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.