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
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, rich trigger terms that match natural developer language, explicit 'Use when' and 'Triggers on' clauses, and clear boundary definitions with cross-references to related skills. The description is comprehensive yet concise, making it easy for Claude to select this skill accurately from a large pool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, connection tuning. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (driver lifecycle, ExecuteQuery, transactions, session config, error handling, data type mapping, connection tuning) and 'when' (explicit 'Use when' clause with specific triggers, plus 'Triggers on' list). Also includes explicit 'Does NOT' boundaries which further clarify when to use it. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a Go developer would use: NewDriver, ExecuteQuery, SessionConfig, ManagedTransaction, neo4j-go-driver, plus contextual phrases like 'Go code that connects to Neo4j' and 'debugging sessions/transactions/result handling'. Includes version references (v5→v6). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting via 'Does NOT handle' clauses that redirect to specific other skills (neo4j-cypher-skill, neo4j-migration-skill). The niche is clearly scoped to the Go driver API rather than Cypher authoring or migration steps. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive skill for the Neo4j Go Driver v6. Its greatest strengths are the fully executable code examples for every API pattern, the clear decision table for choosing the right API, and the thorough common errors troubleshooting table. The main weakness is length — some sections like spatial types and environment variable setup could be moved to reference files to improve token efficiency, though the content itself is well-organized and actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but it's quite long (~350 lines). The spatial types section and some patterns (like the full getEnv helper) add bulk that could be offloaded to reference files. The v5→v6 rename table and URI scheme notes are borderline but useful. Some sections like 'Environment Variables' explain fairly basic Go patterns. | 2 / 3 |
Actionability | Excellent actionable content throughout — every API pattern has complete, executable Go code examples. The ExecuteQuery, managed transactions, explicit transactions, error handling, data types, and batching sections all provide copy-paste ready code with proper imports and error handling. The anti-patterns (❌ markers) are specific and concrete. | 3 / 3 |
Workflow Clarity | The API selection table clearly guides which pattern to use when. The driver lifecycle has explicit validation (VerifyConnectivity), the managed transaction example includes res.Err() checking, and the explicit transaction example shows proper rollback/commit flow. The checklist at the end serves as a comprehensive validation checkpoint. The common errors table provides clear diagnosis→fix workflows. | 3 / 3 |
Progressive Disclosure | The skill has a clear structure with well-organized sections progressing from setup to advanced patterns. It references two specific files (references/advanced-config.md and references/repository-pattern.md) for deeper topics like connection pool tuning and cross-session bookmarks. The WebFetch table provides external references. Content is appropriately split between the main file and references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
66ed0e1
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.