neo4j-spring-data-skill

Use when building Spring Boot applications with Neo4j using Spring Data Neo4j (SDN 7.x/8.x) — @Node entity mapping, @Relationship, @RelationshipProperties, Neo4jRepository, ReactiveNeo4jRepository, @Query annotations, application.yml configuration, projections, Neo4jClient, Neo4jTemplate, transactions, auditing, or Spring AI Neo4jVectorStore vector search. Does NOT handle raw Java driver code without Spring — use neo4j-driver-java-skill. Does NOT handle Cypher query authoring — use neo4j-cypher-skill. Does NOT handle driver version upgrades — use neo4j-migration-skill.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

A comprehensive, highly actionable reference whose code examples are copy-paste ready and whose checklist adds real verification value. Its main weaknesses are a broken bundle reference (neo4j-client.md) and a large amount of inlined content that progressive disclosure would normally move into separate files.

Suggestions

Create references/neo4j-client.md (or fix the link at line 367) so the signaled 'Full API' reference resolves to a real file.

Move the bulkier inline material — the full Neo4jClient fluent-API examples and the multi-case entity-mapping catalog — into one-level-deep reference files, keeping SKILL.md as a tighter overview with key examples.

Consolidate the repeated 'collect(r), collect(p)' guidance into one authoritative spot and cross-reference it from the Checklist and Common Errors table to remove the four-way restatement.

Dimension	Reasoning	Score
Conciseness	Dense, code-first content that assumes Claude's competence with no beginner-level padding, but the critical "collect(r), collect(p)" rule is restated across four places (@Query examples, Common Errors table, the dedicated Relationship Loading section, and the Checklist), which is minor redundancy that could be tightened.	4 / 5
Actionability	Provides copy-paste-ready, executable code throughout — Maven/Gradle deps, application.yml, @Node/@Relationship entities, repository interfaces, @Query with $param binding, Neo4jClient fluent API, @Transactional services, and Spring AI vector store usage — covering the common cases fully.	5 / 5
Workflow Clarity	While not a single linear process, the closing Checklist supplies explicit verification checkpoints and the Common Errors table provides error-recovery guidance for database (destructive/batch) operations; minor gaps remain in explicit validate→fix→retry feedback loops.	4 / 5
Progressive Disclosure	Sections are well-organized with headers and a clear References list, but the body inlines ~485 lines of material that could be split, and one signaled reference — references/neo4j-client.md (line 367) — does not exist in the references/ bundle (only modeling-pitfalls.md is present), leaving a broken link alongside content that should be separate.	3 / 5
	Total	16 / 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 highly specific, well-scoped description that clearly states both capability and trigger conditions while actively routing away from adjacent skills. Its only weakness is a slight lean toward annotation-level jargon over colloquial synonyms in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and lists many concrete capabilities — "@Node entity mapping, @Relationship, @RelationshipProperties, Neo4jRepository, ReactiveNeo4jRepository, @Query annotations, application.yml configuration, projections, Neo4jClient, Neo4jTemplate, transactions, auditing, or Spring AI Neo4jVectorStore vector search" — which is comprehensive coverage matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ("building Spring Boot applications with Neo4j using Spring Data Neo4j" plus the capability list) and when ("Use when building Spring Boot applications with Neo4j...") with concrete trigger phrases, matching the anchor for clearly answering both what AND when.	5 / 5
Trigger Term Quality	Strong keyword coverage with natural domain terms ("Spring Data Neo4j", "SDN", "Neo4jRepository", "application.yml", "vector search", "projections", "transactions", "auditing"), but heavy on annotation jargon and missing a few common lay phrasings a user might say (e.g. "Neo4j with Spring Boot", "graph database with Spring"), so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Spring Data Neo4j via SDN) and explicitly disambiguates from sibling skills via three "Does NOT handle ... use neo4j-*-skill" clauses, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: neo4j-contrib/neo4j-skills
Path: neo4j-spring-data-skill/SKILL.md
Commit: a3627d2

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.