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.

94

1.28x
Quality

92%

Does it follow best practices?

Impact

100%

1.28x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

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 high-quality, well-structured skill that provides comprehensive, actionable guidance for Neo4j Java Driver v6. Its strengths are excellent decision tables (API selection, URI schemes, data types), concrete executable examples with anti-patterns, and good progressive disclosure to reference files. The main weakness is moderate verbosity — the Object Mapping section and some code examples could be tightened, and more content could potentially be pushed to reference files to reduce the main document's token footprint.

Suggestions

Consider moving the Object Mapping section (especially nested mapping) to a reference file, keeping only a brief example and pointer in the main skill to reduce token count.

DimensionReasoningScore

Conciseness

The skill is generally efficient and avoids explaining basic concepts, but it's quite long (~400 lines). Some sections like Object Mapping include redundant examples (two ways to map shown with full code blocks when one would suffice). The Common Errors table is excellent and dense, but the overall document could be tightened by moving more content to reference files.

2 / 3

Actionability

Excellent actionability throughout — every section includes fully executable Java code with correct imports/syntax, specific Maven/Gradle coordinates, concrete environment variable patterns, and clear anti-patterns with fixes. The code examples are copy-paste ready and cover both correct and incorrect usage patterns.

3 / 3

Workflow Clarity

The 'Choosing the Right API' decision table clearly guides API selection. Explicit transaction handling includes proper error recovery with rollback wrapped in try/catch and addSuppressed. The document addresses commit uncertainty and idempotency requirements. The checklist at the end serves as a validation checkpoint for implementations.

3 / 3

Progressive Disclosure

Clear structure with well-signaled references to async-reactive and advanced-config files for deeper topics. The main document covers the essential 80% use case while pointing to reference files for async/reactive patterns and advanced configuration. External docs are also linked. The 'When to Use / When NOT to Use' section effectively routes to sibling skills.

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 excels across all dimensions. It provides comprehensive, specific capabilities, rich trigger terms that match developer vocabulary, explicit 'Use when' guidance, and outstanding distinctiveness through explicit boundary-setting with related skills. The exclusion clauses are a best practice that significantly reduces conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: driver lifecycle, Maven/Gradle setup, executableQuery, managed transactions, explicit transactions, async/reactive patterns, error handling, data type mapping, connection pool tuning, causal consistency/bookmarks.

3 / 3

Completeness

Clearly answers 'what' (driver lifecycle, setup, transactions, error handling, etc.) and 'when' ('Use when writing Java or Kotlin code that connects to Neo4j via...') with explicit trigger terms. Also includes explicit exclusion boundaries directing to other skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a developer would use: 'Java', 'Kotlin', 'Neo4j', 'GraphDatabase.driver', 'executableQuery', 'SessionConfig', 'executeRead', 'executeWrite', 'TransactionCallback', 'Maven', 'Gradle'. These are exactly the terms a user would mention when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive — explicitly delineates boundaries by naming three related skills it does NOT cover (neo4j-cypher-skill, neo4j-migration-skill, neo4j-spring-data-skill) with specific exclusion criteria. The niche of Neo4j Java Driver v6 is very clear and unlikely to conflict.

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.