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.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An excellent reference skill: lean, executable, with clear sequencing, explicit validation checkpoints, and well-organized progressive disclosure to real bundle files. No meaningful weaknesses to address.

DimensionReasoningScore

Conciseness

Dense and lean throughout — terse tables, ❌/✅ callouts, and copy-paste code with almost no conceptual padding; it assumes Claude's competence and every section earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready Go for driver setup, ExecuteQuery, managed/explicit transactions, error handling, batching, generic helpers, and spatial types, plus a symptom→cause→fix error table and a checklist covering the common cases.

5 / 5

Workflow Clarity

Clear install→config→lifecycle→API-choice→patterns→errors sequence with explicit validation checkpoints (VerifyConnectivity at startup, 'check ok before type-asserting', 'check res.Err() after lazy loops') and a final checklist; destructive/batch ops carry verification so the cap does not apply.

5 / 5

Progressive Disclosure

Overview body with well-signaled, one-level-deep references (advanced-config.md, repository-pattern.md — both real files), appropriately splitting pool tuning and the repository pattern out while keeping core API guidance inline.

5 / 5

Total

20

/

20

Passed

Description

92%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 clear what/when guidance and excellent boundary routing against sibling skills. Its only weakness is relying on API/type identifiers as triggers rather than the full range of natural user phrasings.

Suggestions

Broaden the 'Triggers on' list with natural user-language phrases (e.g., 'connect to Neo4j from Go', 'Neo4j Go session', 'neo4j-go-driver') alongside the API/type identifiers to better match how users phrase the need.

Consider adding the Go file extension or import path as a trigger synonym (e.g., '.go files using neo4j-go-driver') to strengthen natural-term coverage.

DimensionReasoningScore

Specificity

Enumerates many concrete capabilities — 'driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, and connection tuning' — for comprehensive coverage rather than minor gaps.

5 / 5

Completeness

Explicitly answers what ('Covers the Neo4j Go Driver v6 — …') and when ('Use when writing Go code that connects to Neo4j …') with concrete trigger phrases and a dedicated 'Triggers on' clause.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases ('writing Go code that connects to Neo4j', 'neo4j-go-driver v5→v6 migration') and a 'Triggers on' list, but it leans on API/type identifiers over the breadth of natural synonyms and file extensions implied by the top anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Go driver v6) with explicit boundary routing — 'Does NOT handle Cypher query authoring — use neo4j-cypher-skill' and 'Does NOT cover driver version migration steps — use neo4j-migration-skill' — minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.