save-to-graph

Ingest graph-queue JSON into Neo4j with idempotent MERGE-based insertion.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/YH-05/quants --skill save-to-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-to-graph
Source: https://github.com/YH-05/quants/tree/main/.claude/skills/save-to-graph
Command: npx skills add https://github.com/YH-05/quants --skill save-to-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest graph-queue JSON into Neo4j, performing idempotent MERGE-based insertion of nodes and relationships to build a consistent knowledge graph according to KG v2.2.

Core Features & Use Cases

  • Four-phase pipeline: queue detection, node insertion, relationship insertion, and completion handling.
  • Idempotent data loading: MERGE-based operations ensure repeats do not create duplicates.
  • Schema awareness: supports KG v2.2 with 14 node types and 31 relationships, aligning with the provided queue format.

Quick Start

Load a graph-queue JSON file and execute the four-phase pipeline to merge nodes and relationships into Neo4j.

Frequently Asked Questions about save-to-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load JSON data into Neo4j without creating duplicate nodes?

Idempotent MERGE-based insertion loads JSON data into Neo4j without creating duplicate nodes. By using deterministic IDs, repeated pipeline runs update existing graph entries instead of appending duplicates, ensuring a consistent knowledge graph.

What is the best way to build a knowledge graph from a JSON queue in Neo4j?

Building a knowledge graph from a JSON queue involves a four-phase pipeline: queue detection, node insertion, relationship insertion, and completion handling. This process merges 14 node types and 31 relationships according to the KG v2.2 schema.

Does idempotent ETL pipeline ingestion support schema validation for Neo4j?

Idempotent ETL pipeline ingestion supports schema validation for Neo4j. It validates graph-queue JSON against the KG v2.2 schema, ensuring 14 node types and 31 relationships are correctly structured before performing any merge operations.

How do I handle connectivity and queue integrity errors during graph data ingestion?

Robust error handling manages connectivity and queue integrity errors during graph data ingestion. The pipeline detects queue issues and validates data formats before insertion, preventing incomplete JSON loads from corrupting the Neo4j knowledge graph.

Can I use MERGE operations to update an existing Neo4j knowledge graph with new JSON data?

You can use MERGE operations to update an existing Neo4j knowledge graph with new JSON data. The pipeline applies idempotent merges using deterministic IDs, ensuring re-running the JSON queue updates existing nodes and relationships without duplication.