CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

93

1.63x
Quality

92%

Does it follow best practices?

Impact

95%

1.63x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 strong, well-structured skill that provides comprehensive, actionable guidance for the Neo4j Go Driver v6. Its greatest strengths are the executable code examples covering every major API pattern, the clear decision table for API selection, and the thorough common errors table. Minor weakness is some verbosity in sections like spatial types and environment variables that could be more compact without losing utility.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good use of tables and code blocks, but includes some sections that could be trimmed (e.g., spatial types section is quite lengthy, environment variables section explains basic patterns Claude knows, and the getEnv helper is boilerplate). The v5→v6 rename table and URI schemes are borderline — useful but could be more compact.

2 / 3

Actionability

Excellent actionable content throughout — every API pattern has complete, executable Go code examples with proper imports and error handling. The ExecuteQuery, managed transactions, explicit transactions, error handling, data types, and batching sections all provide copy-paste ready code with specific function signatures and options.

3 / 3

Workflow Clarity

The skill clearly sequences the driver lifecycle (create → verify → use → close), provides a decision table for choosing the right API, includes explicit validation steps (VerifyConnectivity, res.Err() checking, ok guards on type assertions), and the common errors table serves as a troubleshooting feedback loop. The checklist at the end provides a comprehensive verification step.

3 / 3

Progressive Disclosure

Well-structured with clear sections progressing from setup to advanced patterns. References to external files (references/advanced-config.md, references/repository-pattern.md) are one level deep and clearly signaled with descriptions. WebFetch URLs provided for deeper documentation. The main content stays focused on essential patterns while deferring connection pool tuning and repository patterns to reference files.

3 / 3

Total

11

/

12

Passed

Description

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 developers would naturally use, explicit 'Use when' guidance, and clear boundary definitions with cross-references to related skills. The explicit exclusions ('Does NOT handle...') are a best practice that further reduces conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, connection tuning. These are highly specific 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 scenarios, plus 'Triggers on' keywords). Also includes explicit exclusions with skill redirects.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a Go developer would use: NewDriver, ExecuteQuery, SessionConfig, ManagedTransaction, neo4j-go-driver, 'Go code that connects to Neo4j', 'debugging sessions/transactions/result handling', and even the migration path 'v5→v6'.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche (Neo4j Go Driver v6 specifically). Explicitly delineates boundaries by stating what it does NOT handle and redirecting to other skills (neo4j-cypher-skill, neo4j-migration-skill), minimizing conflict risk.

3 / 3

Total

12

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
neo4j-contrib/neo4j-skills
Reviewed

Table of Contents

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.