CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-driver-java-skill

Neo4j Java Driver v6 — driver lifecycle, Maven/Gradle setup, executableQuery, executeRead/Write managed transactions, explicit transactions, async/reactive patterns, error handling, data type mapping, connection pool tuning, causal consistency/bookmarks. Use when writing Java or Kotlin code that connects to Neo4j via GraphDatabase.driver, executableQuery, SessionConfig, executeRead, executeWrite, or TransactionCallback. Does NOT handle Cypher authoring — use neo4j-cypher-skill. Does NOT cover driver version upgrades — use neo4j-migration-skill. Does NOT cover Spring Data Neo4j (@Node, Neo4jRepository) — use neo4j-spring-data-skill.

80

0.88x
Quality

93%

Does it follow best practices?

Impact

62%

0.88x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a high-quality, executable reference: lean code, concrete error-recovery patterns, and clean progressive disclosure into two real reference files. The only lever is tightening the longer sections (object mapping, performance) to lift conciseness toward the top anchor.

Suggestions

Consider moving the nested object-mapping example (Movie/actors COLLECT block) into a reference file, keeping only the single-record .as(Class) pattern inline, to reduce body length.

Add one short end-to-end 'validate → fix → retry' feedback loop example for the explicit-transaction path to push workflow_clarity to 5.

The version/date notes (6.2.0 [2026-06], 6.2.1 [2026-08]) are time-sensitive; relocate them to a short 'Version notes' subsection or the advanced-config reference so the dependency section stays stable.

DimensionReasoningScore

Conciseness

Dense and fluff-free with no basic-concept explanations and executable examples throughout, but the ~440-line body is large; material like the full object-mapping and performance sections is comprehensive enough that minor trimming or offloading could tighten it further.

4 / 5

Actionability

Fully executable copy-paste Java across every section — driver lifecycle, executableQuery, managed/explicit transactions, error handling, type mapping, UNWIND batching — plus a concrete 'Common Errors' fix table covering the common cases.

5 / 5

Workflow Clarity

Clear sequences with strong checkpoints — verifyConnectivity fail-fast, explicit tx rollback wrapped with addSuppressed, commit-uncertainty idempotency guidance, and a final checklist — but there is no single unified validate→fix→retry pipeline, so it sits just below the top anchor.

4 / 5

Progressive Disclosure

Clear overview in SKILL.md with two well-signaled, one-level-deep references (references/async-reactive.md and references/advanced-config.md, both verified to exist) loaded on demand; content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

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

The description is exemplary: concrete capabilities, natural trigger terms, explicit use-when guidance, and clear deconfliction boundaries against sibling skills. It scores at the top of every dimension with no vague or padded language.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'driver lifecycle, Maven/Gradle setup, executableQuery, executeRead/Write managed transactions, explicit transactions, async/reactive patterns, error handling, data type mapping, connection pool tuning, causal consistency/bookmarks' — comprehensive coverage with no vague filler.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated capability list) and 'when' via a concrete 'Use when writing Java or Kotlin code that connects to Neo4j via...' trigger clause.

5 / 5

Trigger Term Quality

Includes natural API terms a user would actually say — 'Java or Kotlin code that connects to Neo4j', 'GraphDatabase.driver, executableQuery, SessionConfig, executeRead, executeWrite, or TransactionCallback' — with Java/Kotlin synonyms and concrete class/method names.

5 / 5

Distinctiveness Conflict Risk

Three explicit 'Does NOT ... use neo4j-cypher-skill / neo4j-migration-skill / neo4j-spring-data-skill' boundaries carve a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.