neo4j-contrib/gds-agent · Archived

neo4j-graph-data-scientist

Best practices for data science work on graphs using the available tools.

First seen Jul 13, 2026

Installation

$ npx skills add neo4j-contrib/gds-agent --skill neo4j-graph-data-scientist

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 96
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityRequires the gds-agent MCP server (PyPI package gds-agent) and cypher MCP server (PyPI package mcp-neo4j-cypher) connected

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,245 B
  • docs SUMMARY.md 107 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

Workflow

  1. Inspect the database schema first. Never guess labels, types, or property names.
  2. Project a graph. Plugin and session mode have different projection syntax and parameters. Check the graph projection tool description and parameters. For session mode, you need to first create sessions to project graphs onto.
  3. Clean up. dropgraph when a projection is no longer needed. deletesession when a session is no longer needed, and this will automatically drop all graphs projected to this session.
  4. When you see errors, inspect the message and make necessary corrections. If you cannot fix it, consult the detailed [references/troubleshooting.md](references/troubleshooting.md) guide.

Best Practices

  1. Large graphs. When the graph in the DB is large, you might want to consider projecting subgraphs at the start for analysis.

When the projected graph is large, consider mode: "mutate" to store the computed results in the projected graph and then use streamnodeproperties or streamrelationshipproperties to inspect the data.

  1. Long running tools. Certain algorithms (or Cypher queries) are long running. For exploratory work, consider trying them out on smaller projected graphs before executing them on a desirable large projected graph.
  2. Follow general data science best practice. Understand if the task is transductive (over the fixed data) or inductive. For predictive tasks, ensure there is no data leakage.

Formulate hypothesis and design metrics appropriately. Remember all the basic statistics best practices.

  1. Perform additional analysis when needed. You do not need to use solely the Cypher and GDS tools.

For complex data science task, feel free to use other tools or coding capabilities and write ad-hoc scripts that use other libraries, such as pytorch, scikit-learn, pandas, matplotlib, when necessary.