Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced import guide with executable code, explicit validation loops, and real, clearly-signaled reference files. Its main weakness is size: full reference tables and many version-specific annotations live inline in SKILL.md where leaner summaries with pointers to reference files would respect the token budget better.
Suggestions
Move the 'CALL IN TRANSACTIONS — Full Reference' syntax grammar, REPORT STATUS column table, and neo4j-admin key-flags table into a reference file (e.g. references/call-in-transactions-reference.md), keeping only the common patterns and a pointer in SKILL.md.
Consolidate scattered version annotations (2026.02+ dry-run, 2025.12 bad-tolerance default change, 2026.06+/2026.07+ vector and delimiter changes) into a single 'Version-specific changes' or 'Old patterns' section so time-sensitive details don't penalize the main flow.
Trim the batch-size guidance and APOC config tables to the rows that change decisions, or fold them into the same reference file as the CALL IN TRANSACTIONS detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, high-value content with almost no re-teaching of concepts Claude already knows, but at ~500 lines it inlines full syntax references and flag tables, and scatters many time-sensitive version annotations (2026.02+, 2025.12, 2026.06+, 2026.07+) outside any deprecated/versions section, which could be trimmed or consolidated. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready Cypher and bash throughout — e.g. the complete 'LOAD CSV WITH HEADERS ... IN TRANSACTIONS OF 10000 ROWS ON ERROR CONTINUE REPORT STATUS' pattern and the full 'neo4j-admin database import full' command with flags — covering common cases, plus an error-to-fix table for known failures. | 5 / 5 |
Workflow Clarity | Clear sequencing with explicit validation checkpoints and feedback loops appropriate to batch operations: an exact-order pre-import checklist ('Run in this exact order — skipping causes hard-to-debug duplicates'), a method decision table, ON ERROR modes with REPORT STATUS error tracking, and post-import validation that polls populationPercent until indexes are ONLINE. | 5 / 5 |
Progressive Disclosure | Three one-level-deep reference files (driver-batch-write.md, data-importer-gui.md, post-import-refactoring.md) all exist and are clearly signaled both inline and in a References section, but bulk reference material such as the 'CALL IN TRANSACTIONS — Full Reference' syntax tables and the neo4j-admin key-flags table is inlined in SKILL.md rather than split into reference files. | 4 / 5 |
Total | 18 / 20 Passed |