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.

84

1.42x
Quality

89%

Does it follow best practices?

Impact

100%

1.42x

Average score across 2 eval scenarios

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 tightly written, highly actionable API reference with good progressive disclosure to two real bundle files. Its main gaps are minor redundancy between the Checklist and Common Errors table and the absence of an explicit post-write validation loop for batch operations.

Suggestions

Collapse the final Checklist into the Common Errors table (or vice versa) to remove duplicated guidance and recover tokens.

Add an explicit validate-after-batch-write step (e.g. compare written row count to input list, or query-back verification) to give UNWIND batch writes a feedback loop.

Drop the 'When NOT to Use' section in the body since the same boundaries are already stated in the frontmatter description.

DimensionReasoningScore

Conciseness

Dense, table-driven prose that assumes Java/Neo4j knowledge and avoids explaining basics, but the trailing Checklist duplicates the Common Errors table and the 'When NOT to Use' block re-states the description's boundaries — minor trimmable redundancy keeps it just below a 5.

4 / 5

Actionability

Copy-paste-ready Java for executableQuery, managed/explicit transactions, error handling, object mapping, UNWIND batching, and pool tuning covers the common cases fully — matches the score-5 anchor.

5 / 5

Workflow Clarity

Clear sequencing via the 'Choosing the Right API' decision table, explicit-vs-managed selection rules, callback rules, and a verification Checklist, plus commit-uncertainty feedback and idempotent-write guidance; falls just short of 5 because batch/destructive write patterns lack an explicit post-write validate-and-retry feedback loop.

4 / 5

Progressive Disclosure

Core patterns stay inline while async/reactive and advanced config are offloaded to two real, one-level-deep files clearly signaled in a References section with content descriptions — matches the score-5 anchor.

5 / 5

Total

18

/

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.

The description is specific, complete, and sharply bounded with explicit 'Does NOT' carve-outs to sibling skills. Its only weakness is a reliance on API symbol names over natural-language synonyms in the trigger phrasing.

DimensionReasoningScore

Specificity

Lists many 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 of specific actions, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated capabilities) and 'when' ('Use when writing Java or Kotlin code that connects to Neo4j via ...'), with concrete trigger phrases — a clear match for the score-5 anchor.

5 / 5

Trigger Term Quality

Good coverage of API-level trigger terms a developer would cite ('Java or Kotlin code that connects to Neo4j', 'GraphDatabase.driver', 'executableQuery', 'SessionConfig', 'executeRead', 'executeWrite', 'TransactionCallback'), but leans heavily on technical symbols with fewer natural-language synonyms, so it sits just below the comprehensive-synonym bar of 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Neo4j Java Driver v6) plus three explicit 'Does NOT handle ... use neo4j-*-skill' boundaries for Cypher, migration, and Spring Data, giving minimal conflict risk — matches the score-5 anchor.

5 / 5

Total

19

/

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.