CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

85

1.05x
Quality

88%

Does it follow best practices?

Impact

72%

1.05x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable and well-structured import skill with excellent workflow clarity, explicit validation checkpoints, and comprehensive error handling. Its main weakness is length — at 400+ lines it pushes the boundary of conciseness, with some content (detailed flag tables, batch size guidance) that could be offloaded to reference files. The referenced bundle files (driver-batch-write.md, data-importer-gui.md, post-import-refactoring.md) are not provided, making it impossible to verify progressive disclosure fully.

Suggestions

Move detailed reference tables (neo4j-admin key flags, REPORT STATUS columns, batch size guidance) to a references/import-reference.md file to reduce the main SKILL.md length

Provide the referenced bundle files (references/driver-batch-write.md, references/data-importer-gui.md, references/post-import-refactoring.md) to support the progressive disclosure structure

DimensionReasoningScore

Conciseness

The skill is comprehensive and mostly efficient, but its sheer length (~400+ lines) includes some redundancy (e.g., APOC verification mentioned twice, batch size guidance repeated in different sections). Some sections like the full REPORT STATUS column table and key flags table could be trimmed or moved to references. However, most content is genuinely useful and not explaining things Claude already knows.

2 / 3

Actionability

Excellent actionability throughout — every section provides fully executable Cypher queries, bash commands, and concrete header file formats. The LOAD CSV patterns include complete type coercion, null handling, and relationship import examples that are copy-paste ready. The neo4j-admin command includes all necessary flags with real examples.

3 / 3

Workflow Clarity

Outstanding workflow clarity with explicit sequencing (constraints BEFORE import, nodes BEFORE relationships, additional indexes AFTER import), validation checkpoints (post-import count verification, index population polling, null key spot checks), and error recovery (ON ERROR modes table, REPORT STATUS usage). The pre-import checklist enforces exact ordering with clear rationale for each step.

3 / 3

Progressive Disclosure

References section links to external docs and internal files (references/driver-batch-write.md, references/data-importer-gui.md, references/post-import-refactoring.md), but no bundle files are provided to support these references. The main SKILL.md is quite long and some detailed reference tables (key flags, REPORT STATUS columns, batch size guidance) could be moved to reference files. The driver batch write pattern appropriately defers to a reference file.

2 / 3

Total

10

/

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 highly specific capabilities, rich natural trigger terms, explicit 'Use when' guidance, and outstanding distinctiveness through explicit negative boundary clauses that reference sibling skills. This is a model example of a well-crafted skill description.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and tools: LOAD CSV, CALL IN TRANSACTIONS, neo4j-admin database import full, apoc.load.csv/json, apoc.periodic.iterate, driver batch writes. Also enumerates specific sub-topics like header file format, type coercion, null handling, ON ERROR modes, etc.

3 / 3

Completeness

Clearly answers both 'what' (structured data import into Neo4j with specific methods and topics) and 'when' (explicit 'Use when importing CSV/JSON/Parquet files, migrating relational data to graph, or bulk-loading large datasets'). Also includes explicit negative boundaries with 'Does NOT handle' clauses directing to other skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'importing CSV/JSON/Parquet files', 'migrating relational data to graph', 'bulk-loading large datasets', 'LOAD CSV', 'neo4j-admin import'. These are terms a user would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive — explicitly delineates boundaries with three other named skills (neo4j-document-import-skill, neo4j-cypher-skill, neo4j-cli-tools-skill) using 'Does NOT handle' clauses, making conflict risk very low.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (502 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

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.