neo4j-driver-go-skill

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.

1.63x

Quality

86%

Does it follow best practices?

Impact

95%

1.63x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable driver reference with strong code examples, a useful decision table, and a verification checklist. It is held back from top marks by minor verbosity/dues (duplicated lines, URI-scheme overlap with a reference file) and content that could be pushed one level deeper into references.

Suggestions

Remove the duplicate 'Load on demand:' line in the References section.

Move the detailed Spatial Types section into a reference file (or references/advanced-config.md) and keep only a one-line pointer plus the most common 2D WGS-84 example inline.

Drop the inline URI-scheme list at line 89 since references/advanced-config.md already contains a URI Schemes table, or vice versa, to avoid maintaining the same list twice.

Dimension	Reasoning	Score
Conciseness	Mostly lean — tables for API choice and data types, tight ❌-marked pitfalls, copy-paste code — but a few padded spots: 'Load on demand:' is duplicated on adjacent lines and the URI-scheme list repeats content also present in references/advanced-config.md.	4 / 5
Actionability	Fully executable Go throughout: NewDriver setup, ExecuteQuery, managed/explicit transactions, error handling with errors.As, generic helpers, and spatial types are all copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	The 'Choosing the Right API' decision table, 'Common Errors' cause→fix table, and final Checklist provide clear checkpoints and error-recovery feedback for batch/database operations, but it reads as a reference rather than a tightly sequenced validate→fix→retry workflow.	4 / 5
Progressive Disclosure	Good structure with two real one-level-deep references (advanced-config.md, repository-pattern.md) clearly signaled in the References section, but detailed inline material such as the full Spatial Types section and Data Types table could arguably live in reference files, and the duplicated 'Load on demand:' line is a small navigation flaw.	4 / 5
	Total	17 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit trigger terms and clear boundary clauses against sibling skills. Its one weakness is an internal contradiction: the 'Use when' clause invites v5→v6 migration work that the 'Does NOT cover' clause then disclaims.

Suggestions

Remove 'or working with neo4j-go-driver v5→v6 migration' from the 'Use when' clause so the trigger guidance agrees with the later 'Does NOT cover driver version migration steps' exclusion.

Consider adding the Go file extension or import path (e.g. 'neo4j-go-driver/v6') to the trigger list to catch users who paste import errors.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, and connection tuning' — giving comprehensive coverage rather than vague abstractions.	5 / 5
Completeness	Clearly states both what ('Covers the Neo4j Go Driver v6 — …') and when ('Use when writing Go code that connects to Neo4j …'), but the 'when' clause lists 'neo4j-go-driver v5→v6 migration' while a later sentence excludes migration steps, making the trigger condition internally contradictory.	4 / 5
Trigger Term Quality	Includes natural user phrasing ('writing Go code that connects to Neo4j', 'setting up NewDriver or ExecuteQuery', 'neo4j-go-driver') plus an explicit trigger list (NewDriver, ExecuteQuery, SessionConfig, ManagedTransaction), covering both conversational and API-level terms.	5 / 5
Distinctiveness Conflict Risk	Explicit 'Does NOT handle Cypher query authoring — use neo4j-cypher-skill' and 'Does NOT cover driver version migration steps — use neo4j-migration-skill' carve out a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: neo4j-contrib/neo4j-skills
Path: neo4j-driver-go-skill/SKILL.md
Commit: 02ad354

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.