Neo4j Graph Database

Trust Score 76/100

from better-openclaw56

Run Cypher queries and manage nodes/relationships against a local Neo4j instance exposed in the Docker network.

triggers:cypherneo4jcreate nodematch returnMERGEgraph query

GitHub SKILL.md

What it does

This skill provides examples and guidance for querying and mutating a Neo4j graph database available inside a Docker network. It shows how to POST Cypher statements to Neo4j's HTTP transaction endpoint, create nodes and relationships, and prefer Bolt for application connections. The skill is aimed at agents that need to read or update graph data programmatically.

When to use it

Use this skill when an agent needs to inspect graph structures, run parameterised Cypher queries, create or merge nodes/relationships, or index properties for performance. Suitable for debugging graph data, seeding test data, or integrating graph queries into automation workflows.

What's included

Scripts: none in the skill file, but concrete curl examples that show how to call the HTTP transaction API, including parameterised statements.
References: none bundled.
Instructions: examples for MATCH/RETURN, CREATE with parameters, and operational tips (use MERGE to avoid duplicates, create indexes, prefer Bolt for app connections). Emphasises parameterised queries to prevent injection.

Compatible agents

Terminal and script-capable agents that can issue HTTP requests or use Neo4j drivers (agents with curl, HTTP or DB driver support).

Audit Summary

A straightforward skill that provides curl-based Cypher query examples for interacting with a Neo4j instance via its HTTP API. No bundled scripts — purely instructional. Template variables for host/port/password are used appropriately, and the tips section includes good practices like parameterized queries and MERGE over CREATE. Minor security note: password passed via curl -u flag on command line could be visible in process listings.

Watch Out

Requires a running Neo4j instance in Docker network
NEO4J_PASSWORD env var must be set
Password visible in process list via curl -u flag

Notes

Clean, minimal skill. No scripts to audit. The curl examples use env vars for credentials which is acceptable, though ideally Neo4j auth would be passed via header or config file rather than CLI arg.

Information

Repository: better-openclaw
Stars: 56
Installs: 0

Trust Score

Overall76

Security88

Code Quality65

Architecture62

Usefulness58

Related Skills

Yielding Bear — Unified LLM Routing

A unified LLM routing API that automatically routes requests to the cheapest capable model across providers to reduce inference cost by ~60-80%.

Sync Production Database to Development

Run a safe, scripted workflow to download production database dumps and restore them into a development environment (download-only and restore options).

Retriever (Membrane) Integration

Integrate with Retriever via the Membrane CLI to search, query, and proxy Retriever data (documents, snippets, queries) with built-in auth and pagination.

LAP CLI

CLI for compiling, searching, and managing API specifications into a compact agent-native format and generating/installing skills from specs.

Audit Agents/Skills/Commands

Run a quantitative quality audit on agents, skills, and commands to check production readiness and get prioritized recommendations.

Moltbook

Agent-oriented social network client: post dream insights, read feeds, comment, and engage with agent communities (Moltbook API integration).

Supabase SDK Patterns (TypeScript & Python)

Production-ready patterns for using Supabase clients in TypeScript and Python: client initialization, typed queries, auth, realtime, storage, RPC, and error-han

Evolve SDK

SDK and guides for building and running CLI agents in secure sandboxes (TypeScript & Python).

Back to Skills