neo4j-import-skill

Import structured data into Neo4j — LOAD CSV, CALL IN TRANSACTIONS, neo4j-admin database import full (offline bulk), apoc.load.csv/json, apoc.periodic.iterate, driver batch writes. Covers method selection, header file format, type coercion, null handling, ON ERROR modes, CONCURRENT TRANSACTIONS, pre-import constraint setup, and post-import validation. Use when importing CSV/JSON/Parquet files, migrating relational data to graph, or bulk-loading large datasets. Does NOT handle unstructured document/PDF/vector chunking pipelines — use neo4j-document-import-skill. Does NOT handle live app write patterns (MERGE/CREATE) — use neo4j-cypher-skill. Does NOT handle neo4j-admin backup/restore/config — use neo4j-cli-tools-skill.

1.25x

Quality

88%

Does it follow best practices?

Impact

100%

1.25x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 dense, highly actionable skill body with executable examples, explicit ordered checklists, and real validation feedback loops for destructive/batch operations. The main weakness is conciseness/structure: a large amount of reference material is inlined in SKILL.md rather than pushed to bundle files, slightly straining the context budget.

Suggestions

Move the full CALL IN TRANSACTIONS reference (syntax, REPORT STATUS columns, ON ERROR modes table) into a references/ file and keep only the load-bearing pattern inline in SKILL.md, linking out for the rest.

Extract the neo4j-admin header-file format tables and key-flags reference into a dedicated references/neo4j-admin-import.md, leaving the command skeleton and dry-run/validation steps in the main body.

Trim the version-number-heavy annotations (e.g. "2026.02+", "2025.12", "2026.06+") into a single "version compatibility" note or a deprecated/old-patterns subsection, as time-sensitive inline tags add tokens without aiding execution.

Dimension	Reasoning	Score
Conciseness	Largely lean — tables for ON ERROR modes, batch sizes, and error→fix mappings compress a lot of reference material without explaining concepts Claude already knows — but the ~500-line body inlines full reference content (e.g. the entire CALL IN TRANSACTIONS syntax and header-format tables) that could arguably live in a bundle file, leaving minor over-density.	4 / 5
Actionability	Fully executable, copy-paste-ready Cypher/bash examples for every method (LOAD CSV with type coercion, neo4j-admin import command, apoc.periodic.iterate), plus concrete config tables, header-file templates with sample data rows, and a Common Errors table mapping real error strings to fixes — covering the common cases comprehensively.	5 / 5
Workflow Clarity	Explicit multi-step workflows with validation checkpoints throughout: an ordered Pre-Import Checklist ("Run in this exact order"), a destructive neo4j-admin offline load with a --dry-run validation step, and a Post-Import Validation section that polls populationPercent until 100 and gates production queries behind ONLINE indexes — exactly the validate→fix→retry feedback loop the rubric rewards.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references to real bundle files ([driver-batch-write.md](references/driver-batch-write.md), [data-importer-gui.md](references/data-importer-gui.md), [post-import-refactoring.md](references/post-import-refactoring.md), confirmed present) plus external manual links, but the body itself carries substantial bulk reference material inline (full CALL IN TRANSACTIONS reference, header-format tables) that could be split out for cleaner separation.	4 / 5
	Total	18 / 20 Passed

Description

87%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 precise, well-scoped description that names concrete import methods and trigger phrases while explicitly carving out adjacent skills. Minor keyword-synonym gaps keep trigger_term_quality and specificity just below 5.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several specific concrete actions — "LOAD CSV, CALL IN TRANSACTIONS", "neo4j-admin database import full (offline bulk)", "apoc.load.csv/json", "apoc.periodic.iterate", "driver batch writes" — plus sub-topics like "type coercion, null handling, ON ERROR modes", though a couple are listed as bare keywords rather than fully fleshed actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both: "what" (import methods, header format, type coercion, null handling, validation) and "when" via the concrete "Use when importing CSV/JSON/Parquet files, migrating relational data to graph, or bulk-loading large datasets" clause, plus explicit "Does NOT handle…" scoping.	5 / 5
Trigger Term Quality	Strong natural keyword coverage — "importing CSV/JSON/Parquet files", "migrating relational data to graph", "bulk-loading large datasets" — but misses a few common synonyms a user might say (e.g. "Cypher", "MERGE/upsert", file extensions like .csv/.json) so it is not quite comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (structured/bulk import) with explicit negative-scoping against sibling skills (neo4j-document-import-skill, neo4j-cypher-skill, neo4j-cli-tools-skill), minimizing the chance of triggering for the wrong skill.	5 / 5
	Total	18 / 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
skill_md_line_count	SKILL.md is long (501 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: neo4j-contrib/neo4j-skills
Path: neo4j-import-skill/SKILL.md
Commit: 02ad354

Reviewed: 3 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.