Index of every page on this site: llms.txt
All skills
relatedb avatar

/bundle

@58414e9
by relatedbrelatedb/relate409 stars
35
Run it yourself

Relate is an embedded openCypher graph database with a single-binary CLI. Use this skill when the user wants to run Cypher queries, manage a local graph database, or embed it from Python; its focused references cover vector search, geospatial, operations, and agent safety.

  • 18 files
  • 116.4 KB
  • Updated 2 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/relatedb/relate/bundle

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencespull.md

≈554 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Pull from Neo4j / Aura

relate pull [--from FILE] --query Q [--param N=V] --database PATH
  • --from FILE — KEY=VALUE env file (NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, optional NEO4J_DATABASE). Same format as Aura Created credentials and neo4j-cli --env-out-file. Omit --from to use those process environment variables (NEO4J_USER aliases NEO4J_USERNAME).
  • --query Q — required shape query (file path or inline). Must RETURN nodes, relationships, or paths — not scalars or aggregates.
  • --param N=V — source query parameter (repeatable).
  • --database PATH — destination directory or .rl bundle. :memory: is rejected.

NEO4J_URI is an http(s) Query API origin (e.g. https://host:7473); a Bolt neo4j://host:7687 maps to http://host:7474, an Aura neo4j+s:// URI to https://<host>/. The hosted demo's Query API is https://demo.neo4jlabs.com:7473 (database companies).

The command talks HTTP Query API v2, upserts the subgraph (source-scoped union on remote elementId; overlapping pulls reuse existing local elements), then carries the source schema (ADR-0201): SHOW CONSTRAINTS / SHOW INDEXES rows are replayed as standalone CREATE … IF NOT EXISTS statements (uniqueness / existence / key / property-type constraints and RANGE / TEXT / POINT indexes; constraint-backing, offline, LOOKUP, FULLTEXT and VECTOR rows are filtered or skipped with a stderr note — schema replay never fails a pull). It checkpoints, prints pulled N new / M reused nodes, P new / Q reused rels (+ C constraints, I indexes; S schema skipped) to PATH, and exits.

Pulled values keep their Cypher type (ADR-0181): pull asks the source for the typed Query API v2 JSON media type, so POINT, DATE, TIME, DATETIME, ZONED DATETIME, DURATION, UUID, VECTOR, and every other source type are stored as those types. A property the engine cannot represent — a byte array (Base64), an Unsupported value, an unparseable payload, or an untagged cell — fails the pull with exit 1 and a typed wire decode failed: … error naming the element id and property key. The full source-type → stored-type table is in docs/api/cli/spec.md.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 58414e9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
version
{
  "{ VERSION }": null
}

README badge

README badge for relatedb/relate/bundle