Agent skill

Neo4j Getting Started Skill

by neo4j-contrib in neo4j-contrib/neo4j-skills

Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build.

MITAuto-check: warningsTesting & QA

Install Neo4j Getting Started Skill

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add neo4j-contrib/neo4j-skills --skill neo4j-getting-started-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install neo4j-contrib/neo4j-skills neo4j-getting-started-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/neo4j-contrib/neo4j-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/neo4j-getting-started-skill .claude/skills/neo4j-getting-started-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
neo4j-getting-started-skill
GitHub stars
114
Token cost
~4.3k tokens
SKILL.md length
1,398 words
Files
18 (incl. scripts, references)
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build.

  • Works in 8 steps: prerequisites → context → provision → …
  • Starting a new Neo4j project from scratch
  • SKILL.md covers When to Use, When NOT to Use, Project Structure and Progress Tracking, plus 12 more sections
  • Runs Python scripts from its folder; calls python3 and pip; needs NEO4J_PASSWORD

What it does

Neo4j Getting Started Skill is an agent skill from neo4j-contrib/neo4j-skills. Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building a notebook or app, or running the full onboarding pipeline. Time budget ≤15 min autonomous, ≤90 min HITL. Does NOT cover Cypher query authoring — use neo4j-cypher-skill. Does NOT cover driver…

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts and reference files (for example `AGENTS.md`, `README.md` and `references/0-prerequisites.md`). Compatibility notes: claude-code, cursor, windsurf, any-agent-with-bash

It sits in Testing & QA, covering Test data and fixtures. It works with Neo4j. The repository describes itself as: Neo4j Skills for Coding and other Agents including Cypher. The licence is MIT.

When your agent uses it

  • Starting a new Neo4j project from scratch
  • Provisioning Aura
  • Generating synthetic data
  • Building a notebook

Example prompts

  • “Use the neo4j-getting-started-skill skill to orchestrate zero-to-running-app in 8 stages — prerequisites → context → provision → model → load →…”
  • “/neo4j-getting-started-skill”

Requirements

  • Python 3
  • Docker
  • Compatibility (from SKILL.md): claude-code, cursor, windsurf, any-agent-with-bash
  • Pre-approved tools (allowed-tools): Bash, WebFetch, Read, Write, Edit, mcp__neo4j__read-cypher, mcp__neo4j__write-cypher, mcp__neo4j__get-schema, mcp__neo4j__list-gds-procedures, mcp__neo4j_data_modeling__validate_data_model, mcp__neo4j_data_modeling__visualize_data_model

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. prerequisites
  2. context
  3. provision
  4. model
  5. load
  6. explore
  7. query
  8. build

What it can do on your machine

Read from SKILL.md and the folder at commit bb30e1f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • WebFetch
    • Read
    • Write
    • Edit
    • mcp__neo4j__read-cypher
    • mcp__neo4j__write-cypher
    • mcp__neo4j__get-schema
    • mcp__neo4j__list-gds-procedures
    • mcp__neo4j_data_modeling__validate_data_model

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • graphacademy.neo4j.com
    • browser.neo4j.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • NEO4J_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    claude-code, cursor, windsurf, any-agent-with-bash

    From compatibility in the SKILL.md frontmatter.

Context cost

Neo4j Getting Started Skill loads about 4.3k tokens when it runs, and up to ~37k if it reads all its reference files. Until then it costs about 169 tokens; SKILL.md has 1,398 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~169
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~37k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • NoteMentions a .env fileSKILL.md:51
    .env                    ← DB credentials (gitignored, loaded by python-dotenv)
  • NoteMentions a .env fileSKILL.md:78
    Root-level files (`.env`, `requirements.txt`, app code) stay at root because tooling expects them there. Everything else
  • NoteMentions a .env fileSKILL.md:181
    ` binary is reachable; `.gitignore` has `.env` entry.
  • NoteMentions a .env fileSKILL.md:195
    Neo4j database and save credentials to `.env`.
  • NoteMentions a .env fileSKILL.md:197
    **Completes when**: `.env` exists with `NEO4J_URI/USERNAME/PASSWORD/DATABASE`; connectivity verified.
  • NoteMentions a .env fileSKILL.md:198
    ndition**: `DB_TARGET=existing` → write `.env` from user credentials, proceed to `3-model`.
  • NoteMentions a .env fileSKILL.md:259
    GET=existing` | Skip `provision`; write `.env` from user creds; go to `model` |
  • WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:269
    CI-like, all context provided upfront): never pause for approval at any stage; auto-approve all decisions; proceed immed
  • NoteMentions a .env fileSKILL.md:312
    Use `NEO4J_PASSWORD` from `.env` to connect, then run:
  • NoteMentions a .env fileSKILL.md:323
    ypher` | Constraints + indexes | `source .env && cypher-shell -a $NEO4J_URI -u $NEO4J_USERNAME -p $NEO4J_PASSWORD --file

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from neo4j-contrib/neo4j-skills at commit bb30e1f, republished under its MIT licence (© neo4j-contrib). 1,398 words, ~4,303 tokens.

Download SKILL.mdSave it as .claude/skills/neo4j-getting-started-skill/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.
name
neo4j-getting-started-skill
description
Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building a notebook or app, or running the full onboarding pipeline. Time budget ≤15 min autonomous, ≤90 min HITL. Does NOT cover Cypher query authoring — use neo4j-cypher-skill. Does NOT cover driver upgrades or Cypher migration — use neo4j-migration-skill. Does NOT cover CLI/admin tasks on an existing DB — use neo4j-cli-tools-skill.
allowed-tools
Bash, WebFetch, Read, Write, Edit, mcp__neo4j__read-cypher, mcp__neo4j__write-cypher, mcp__neo4j__get-schema, mcp__neo4j__list-gds-procedures, mcp__neo4j_data_modeling__validate_data_model, mcp__neo4j_data_modeling__visualize_data_model
compatibility
claude-code, cursor, windsurf, any-agent-with-bash
version
1.0.6

Neo4j Getting-Started Skill

Guide a user or agent from zero to a working Neo4j application by executing the 8 stages below in order.

At the start of each stage: read the corresponding ${CLAUDE_SKILL_DIR}/references/<stage-name>.md file and follow its instructions. Only load the stage you are currently executing — not all at once.

"User" means both a human developer and an autonomous coding agent.


When to Use

  • New Neo4j project from scratch (local/Docker/Aura)
  • Full onboarding: zero → DB → model → load → app
  • Generating synthetic data for demos or dev

When NOT to Use

  • Cypher authoring on existing project → neo4j-cypher-skill
  • Driver upgrades / Cypher migration → neo4j-migration-skill
  • Admin on existing DB (backup, restore, import) → neo4j-cli-tools-skill

Project Structure

All generated code, data, scripts, queries, and notebooks must be written to the working directory so the user can inspect, reuse, and re-run them after the session ends. Never generate output only as text in the conversation — always write it to a file.

Organize files into this layout. Create subdirectories before writing files.

.env                    ← DB credentials (gitignored, loaded by python-dotenv)
aura.env                ← Aura API credentials (gitignored, never overwrite)
progress.md             ← stage-by-stage progress (this skill writes it)
requirements.txt        ← Python dependencies

schema/
  schema.json           ← graph model definition
  schema.cypher         ← DDL: constraints + indexes
  reset.cypher          ← wipe all data (keep schema)

data/
  generate.py           ← synthetic data generator  (DATA_SOURCE=synthetic)
  import.py             ← CSV/file importer          (DATA_SOURCE=csv or relational)
  *.csv                 ← any provided or generated data files

queries/
  queries.cypher        ← validated Cypher query library

scripts/
  provision_aura.py     ← Aura provisioning script (generated during provision stage)

notebook.ipynb          ← app artifact (root — standard jupyter convention)
app.py                  ← app artifact (root — streamlit run app.py)
main.py                 ← app artifact (root — uvicorn main:app)
graphrag_app.py         ← app artifact (root)

Root-level files (.env, requirements.txt, app code) stay at root because tooling expects them there. Everything else goes in the appropriate subfolder.


Progress Tracking

The skill maintains progress.md in the working directory to support resumability.

On startup:

  1. Check if progress.md exists.
  2. If it exists, find the first pending stage:
    bash
    grep -B1 "^status: pending" progress.md | grep "^###" | head -1
  3. Resume from that stage. Read its context block (the key=value lines beneath the header) to restore DOMAIN, USE_CASE, NEO4J_URI, etc. — do not re-ask the user for information already recorded.
  4. For each completed stage, read every file listed in its files= line before proceeding. These files are the ground truth — do not reconstruct their content from memory.
    • schema/schema.json → re-read before model, load, query, or build stages
    • queries/queries.cypher → re-read before build stage
    • data/generate.py → re-read before import or reset
  5. If progress.md does not exist, start from 0-prerequisites.

On stage completion — update (or create) progress.md:

  • If the stage's ### section already exists, update status: pending → status: done and append any new key=value lines.
  • If the section doesn't exist, append it following the format below.

Format:

markdown
# Neo4j Getting-Started — Progress
<!-- Resume: grep for "status: pending" to find the next stage -->

### 0-prerequisites
status: done

### 1-context
status: done
DOMAIN=social
USE_CASE=friend recommendations
EXPERIENCE=beginner
DB_TARGET=aura-free
DATA_SOURCE=synthetic
APP_TYPE=notebook
EXEC_METHOD=query-api

### 2-provision
status: done
NEO4J_URI=neo4j+s://abc123.databases.neo4j.io

### 3-model
status: done
labels=Person,Post
relationships=FOLLOWS,POSTED
constraints=2

### 4-load
status: done
nodes=200 Person, 50 Post
relationships=1400 FOLLOWS, 300 POSTED

### 5-explore
status: pending

### 6-query
status: pending

### 7-build
status: pending

Execution Protocol

For each stage:

  1. Announce the stage: "## Stage: <name> — <purpose>"
  2. Read ${CLAUDE_SKILL_DIR}/references/<name>.md
  3. Execute the instructions in that file
  4. Verify the stage's completion condition
  5. Update progress.md with status: done and stage-specific context
  6. Proceed to the next stage (HITL: pause for approval first)

If a stage fails, recover using the error guidance in the stage reference file. Do not skip stages unless the skip condition below explicitly permits it.


Stages

Stages run in the numbered order shown. Each depends on the one before it completing successfully (except where a skip condition applies). Read the linked reference file when entering each stage.

0-prerequisites → 1-context → 2-provision → 3-model → 4-load → 5-explore → 6-query → 7-build

Shared capabilities used across multiple stages:

  • Cypher execution: ${CLAUDE_SKILL_DIR}/references/capabilities/execute-cypher.md (3 options; EXEC_METHOD chosen in context)
  • Cypher authoring rules: ${CLAUDE_SKILL_DIR}/references/capabilities/cypher-authoring.md (or defer to neo4j-cypher-authoring-skill)
  • MCP configuration: ${CLAUDE_SKILL_DIR}/references/capabilities/mcp-config.md (used in prerequisites and build)
  • Query validation: ${CLAUDE_SKILL_DIR}/scripts/validate_queries.py — batch-validate all queries in one call (used in query)

0 — prerequisites

Purpose: Verify and install required CLI tools before doing anything else.
Reference: ${CLAUDE_SKILL_DIR}/references/0-prerequisites.md
Completes when: neo4j-mcp binary is reachable; .gitignore has .env entry.
Never skip.


1 — context

Purpose: Collect domain, use-case, experience, infrastructure target, data source, and output type. Detect EXEC_METHOD for Cypher execution.
Reference: ${CLAUDE_SKILL_DIR}/references/1-context.md
Completes when: DOMAIN, USE_CASE, EXPERIENCE, DB_TARGET, DATA_SOURCE, APP_TYPE, EXEC_METHOD are known.
Skip condition: all variables already provided in conversation context.


2 — provision

Purpose: Provision a running Neo4j database and save credentials to .env.
Reference: ${CLAUDE_SKILL_DIR}/references/2-provision.md
Completes when: .env exists with NEO4J_URI/USERNAME/PASSWORD/DATABASE; connectivity verified.
Skip condition: DB_TARGET=existing → write .env from user credentials, proceed to 3-model.


3 — model

Purpose: Design or discover a graph data model suited to the use-case.
Reference: ${CLAUDE_SKILL_DIR}/references/3-model.md
Completes when: schema.json and schema.cypher written.
Skip condition: DATA_SOURCE=demo → use demo schema, proceed to 4-load.
HITL checkpoint (HITL mode only — skip entirely in autonomous mode): show model draft, wait for approval.


4 — load

Purpose: Apply schema constraints, then import data (demo, synthetic, CSV, or documents).
Reference: ${CLAUDE_SKILL_DIR}/references/4-load.md
Depends on: 3-model (constraints must exist before import).
Completes when: node count ≥ 50; import/ scripts written; reset.cypher written.


5 — explore

Purpose: Deliver a visual entry point to the graph — the "it clicks" moment.
Reference: ${CLAUDE_SKILL_DIR}/references/5-explore.md
Completes when: browser URL printed to user, or notebook visualization cell added.
Hard gate — never skip.


6 — query

Purpose: Generate and validate a Cypher query library for the use-case.
Reference: ${CLAUDE_SKILL_DIR}/references/6-query.md
Completes when: queries.cypher has ≥5 queries; ≥2 traversals; ≥3 return results.


7 — build

Purpose: Generate a runnable application, dashboard, notebook, or agent integration.
Reference: ${CLAUDE_SKILL_DIR}/references/7-build.md
Completes when: artifact exists, passes syntax check, returns non-empty use-case results.


Success Gates (all 7 required)

GateStageCondition
db_runningprovisiondriver.verify_connectivity() succeeds
model_validmodel≥2 node labels, ≥1 rel type, ≥1 constraint in DB
data_presentloadMATCH (n) RETURN count(n) ≥ 50
queries_workquery≥5 queries; ≥2 traversals; ≥3 return ≥1 result
graph_visibleexploreBrowser URL or notebook viz delivered to user
app_generatedbuildArtifact exists, passes syntax, returns non-empty results
integration_readybuildMCP config or agent framework code present (if requested)

Show full SKILL.md (576 more words)Show less

Fast Paths

SituationAction
DB_TARGET=existingSkip provision; write .env from user creds; go to model
DATA_SOURCE=demoSkip custom modeling; use demo schema; jump to load
DB_TARGET=existing + data presentSkip provision, model, load; introspect schema; go to explore

HITL vs Autonomous Mode

HITL (conversational): pause after model for model review; pause after load for data review.

Autonomous (CI-like, all context provided upfront): never pause for approval at any stage; auto-approve all decisions; proceed immediately through all 8 stages; print browser URL to stdout; target ≤15 min from DB running.

How to detect autonomous mode — check at the start of stage 1:

Autonomous if ANY of the following are true:

  • The initial prompt contains all of: DOMAIN, USE_CASE, EXPERIENCE, DB_TARGET, DATA_SOURCE, APP_TYPE (or equivalent phrasing like "Domain: X, use-case: Y, ...")
  • The session was started with --auto-approve or similar non-interactive flag
  • All context variables are already recorded in progress.md (resuming an autonomous run)

HITL if: the user opened a fresh conversation without providing full context upfront.

In autonomous mode: every HITL checkpoint in every stage reference file is automatically skipped. Do not ask for approval. Do not say "does this look right?" Do not pause. Continue to the next step immediately.


Final Summary (deliver after all gates pass)

Step 1 — write README.md to the working directory using the template below. Fill in every <placeholder> from progress.md and the actual generated files. This is a required output — do not skip it.

IMPORTANT — portable commands: All re-run commands in README.md MUST use python3 (never an absolute path like /opt/homebrew/bin/python3.14 or /usr/local/bin/python3). The README is shared with others who have different Python installs.

markdown
# <DOMAIN> Graph — <USE_CASE>

A synthetic <DOMAIN> graph built with Neo4j, covering <USE_CASE>.
Generated by the neo4j-getting-started-skill on <date>.

## What's in the graph

| Label | Count | Description |
|-------|-------|-------------|
| <Label> | <N> | <one line> |

**Relationships:** <TYPE1>, <TYPE2>, ...  
**Constraints:** <N> uniqueness constraints applied

## Explore visually

Open in Neo4j Browser:
<browser_url>

Use `NEO4J_PASSWORD` from `.env` to connect, then run:
```cypher
// Starter query — shows the full graph sample
MATCH (n)-[r]->(m) RETURN n, r, m LIMIT 50

Files

FilePurposeRe-run
schema/schema.jsonGraph model—
schema/schema.cypherConstraints + indexessource .env && cypher-shell -a $NEO4J_URI -u $NEO4J_USERNAME -p $NEO4J_PASSWORD --file schema/schema.cypher
schema/reset.cypherWipe data, keep schemasource .env && cypher-shell -a $NEO4J_URI -u $NEO4J_USERNAME -p $NEO4J_PASSWORD --file schema/reset.cypher
data/generate.pyRegenerate synthetic datasource .venv/bin/activate && python3 data/generate.py
data/import.pyRe-import CSVs into Neo4jsource .venv/bin/activate && python3 data/import.py
queries/queries.cypherQuery libraryPaste into Neo4j Browser
<artifact><app type><run command>
requirements.txtPython dependenciessource .venv/bin/activate && pip install -r requirements.txt

(Omit data/generate.py row when DATA_SOURCE=csv; omit data/import.py row when DATA_SOURCE=synthetic.)

Run the app

bash
python3 -m venv .venv     # skip if .venv already exists
source .venv/bin/activate
pip install -r requirements.txt
<run command>

<For FastAPI only — include this section:> Open http://localhost:8000/docs for the interactive API docs.

<For MCP integration — include this section when APP_TYPE includes mcp:>

MCP integration

To query your graph directly from Claude:

Claude Code — copy mcp-claude-code.json into .claude/settings.json:

bash
cp mcp-claude-code.json .claude/settings.json

Then reload Claude Code (/reload or restart). Ask: "What node labels are in my Neo4j database?"

Claude Desktop — merge mcp-claude-desktop.json into ~/Library/Application Support/Claude/claude_desktop_config.json, then restart Claude Desktop.

Available MCP tools: get-schema, read-cypher, write-cypher.

Reset and reload

bash
source .env
cypher-shell -a $NEO4J_URI -u $NEO4J_USERNAME -p $NEO4J_PASSWORD --file schema/reset.cypher
source .venv/bin/activate
python3 data/generate.py   # or skip if using your own CSVs
python3 data/import.py

Sample queries

cypher
// <use-case-specific query 1 — fill in from queries/queries.cypher>
<query>

// <use-case-specific query 2>
<query>

(Cypher comments use //, not --.)

Next steps

  • Explore GraphAcademy to deepen your Neo4j knowledge
  • Edit data/*.csv to change the dataset, then re-run data/import.py
  • Extend the model: add new node labels or relationship types in schema/schema.json

**Step 2 — print this to the conversation:**

✓ Neo4j Getting-Started — Complete

Database: <NEO4J_URI> Browser: https://browser.neo4j.io/?connectURL=<encoded>

── What was generated (keep these files) ─────────────────────── schema/schema.json Graph model definition schema/schema.cypher Re-apply constraints/indexes: cypher-shell ... --file schema/schema.cypher schema/reset.cypher Wipe data, keep schema: cypher-shell ... --file schema/reset.cypher data/generate.py Regenerate synthetic data: source .venv/bin/activate && python3 data/generate.py data/*.csv Source data files — edit to change the dataset data/import.py Re-import from CSVs: source .venv/bin/activate && python3 data/import.py queries/queries.cypher Query library — paste into Neo4j Browser or run with cypher-shell <app-file> <run-command> requirements.txt Install deps: source .venv/bin/activate && pip install -r requirements.txt

── Gates ─────────────────────────────────────────────────────── db_running ✓ model_valid ✓ data_present ✓ queries_work ✓ graph_visible ✓ app_generated ✓ integration_ready ✓/–

── Next steps ──────────────────────────────────────────────────

  • Explore: open the Browser URL → run MATCH (n)-[r]->(m) RETURN n,r,m LIMIT 50
  • Iterate: edit data/*.csv → source .venv/bin/activate && python3 data/import.py (reset first)
  • Learn: https://graphacademy.neo4j.com

Omit lines that don't apply (e.g. omit `data/import.py` when `DATA_SOURCE=synthetic`,
omit `data/generate.py` when `DATA_SOURCE=csv`).

---

## Checklist

- [ ] Prerequisites met (Docker/Python/Java; Aura API key if cloud)
- [ ] DB reachable — `RETURN 1` in cypher-shell
- [ ] Constraints + indexes ONLINE before data load
- [ ] Data loaded — `MATCH (n) RETURN count(n)` > 0
- [ ] queries.cypher: all queries return expected results
- [ ] App/notebook runs end-to-end
- [ ] `.env` gitignored; credentials not hardcoded

© neo4j-contrib, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 17 other files (scripts, references) in neo4j-getting-started-skill of neo4j-contrib/neo4j-skills.

  • SKILL.md
  • AGENTS.md
  • README.md
  • references/0-prerequisites.md
  • references/1-context.md
  • references/2-provision.md
  • references/3-model.md
  • references/4-load.md
  • references/5-explore.md
  • references/6-query.md
  • references/7-build.md
  • references/capabilities/cypher-authoring.md
  • references/capabilities/execute-cypher.md
  • references/capabilities/kg-from-documents.md
  • references/capabilities/mcp-config.md
  • references/domain-patterns.md
  • references/quick-reference.md
  • scripts/validate_queries.py

Open the folder on GitHubat commit bb30e1f

Compare with similar skills

Neo4j Getting Started Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Neo4j Getting Started Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Neo4j Getting Started Skill this skillneo4j-contrib/neo4j-skills114—~4.3kAutomated safety check: WarnMIT
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone
Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk11k—~1.8kAutomated safety check: PassMIT
source-mssql E2E Test Harnessairbytehq/airbyte22k—~4.4kAutomated safety check: PassCustom licence
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0
OpenLogi Device Fixture ContributionAprilNEA/OpenLogi23k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed
  • Official

    Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.

    11k GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Official

    Stands up a throwaway local SQL Server 2022 backend, applies SQL fixtures and runs Airbyte spec, check, discover and read against source-mssql images.

    22k GitHub stars~4.4k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.

    23k GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Official

    Stands up a throwaway local MySQL 8.0 backend, applies SQL fixtures and sweeps the Airbyte spec, check, discover and read commands against a source-mysql image.

    22k GitHub stars~2.6k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from neo4j-contrib/neo4j-skills

All 28 skills in this repo
  • Neo4j Aura Agent Skill

    neo4j-contrib/neo4j-skills

    Manages Neo4j Aura Agents via the v2beta1 REST API — create, list, get, update, delete, and invoke Aura agents backed by an AuraDB instance.

    114 GitHub stars~4.4k tokensUpdated yesterday
    Auto-check: notes
  • Neo4j Cypher Skill

    neo4j-contrib/neo4j-skills

    Generates, optimizes, and validates Cypher 25 queries for Neo4j 2025.x and 2026.x.

    114 GitHub starsUsed in 1 repo~6.1k tokens
    Auto-check passed
  • Neo4j Aura Graph Analytics Skill

    neo4j-contrib/neo4j-skills

    Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, getorcreate, remote graph projection with…

    114 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check: notes
  • Neo4j Aura Provisioning Skill

    neo4j-contrib/neo4j-skills

    Provisions and manages Neo4j Aura instances via CLI (aura-cli v1.7+) or REST API.

    114 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes
  • Neo4j Driver Dotnet Skill

    neo4j-contrib/neo4j-skills

    Neo4j .NET Driver v6 — IDriver lifecycle, DI registration (singleton), ExecutableQuery fluent API, ExecuteReadAsync/ExecuteWriteAsync managed transactions, IResultCursor (FetchAsync/ ToListAsync)…

    114 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check: notes
  • Neo4j Driver Go Skill

    neo4j-contrib/neo4j-skills

    Covers the Neo4j Go Driver v6 — driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, and connection tuning.

    114 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Neo4j Getting Started Skill

What does Neo4j Getting Started Skill do?

Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Neo4j Getting Started Skill is an agent skill from neo4j-contrib/neo4j-skills. Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build.

When should I use Neo4j Getting Started Skill?

Neo4j Getting Started Skill fits situations like: starting a new Neo4j project from scratch; provisioning Aura; generating synthetic data; building a notebook.

How do I install Neo4j Getting Started Skill in Claude Code?

Run `npx skills add neo4j-contrib/neo4j-skills --skill neo4j-getting-started-skill -a claude-code`. Or copy the skill folder (neo4j-getting-started-skill in neo4j-contrib/neo4j-skills) into .claude/skills/neo4j-getting-started-skill in your project. Claude Code loads it when a task matches its description.

How do I install Neo4j Getting Started Skill in Codex?

Run `npx skills add neo4j-contrib/neo4j-skills --skill neo4j-getting-started-skill -a codex`. Or copy the skill folder (neo4j-getting-started-skill in neo4j-contrib/neo4j-skills) into .agents/skills/neo4j-getting-started-skill in your project. Codex loads it when a task matches its description.

Can I use Neo4j Getting Started Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add neo4j-contrib/neo4j-skills --skill neo4j-getting-started-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/neo4j-getting-started-skill, .gemini/skills/neo4j-getting-started-skill, .github/skills/neo4j-getting-started-skill and .opencode/skills/neo4j-getting-started-skill in your project.

What does Neo4j Getting Started Skill need to run?

Going by SKILL.md and its folder, Neo4j Getting Started Skill needs Python for the scripts in its folder, the command-line tools its instructions call (python3 and pip) and credentials named NEO4J_PASSWORD. Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Bash, WebFetch, Read, Write, Edit, mcp__neo4j__read-cypher, mcp__neo4j__write-cypher, mcp__neo4j__get-schema, mcp__neo4j__list-gds-procedures, mcp__neo4j_data_modeling__validate_data_model, mcp__neo4j_data_modeling__visualize_data_model. Compatibility (from SKILL.md): claude-code, cursor, windsurf, any-agent-with-bash.

Does Neo4j Getting Started Skill access the network?

SKILL.md names 2 domains. As links in the text: graphacademy.neo4j.com and browser.neo4j.io. This is read from the text; nothing was executed.

Is Neo4j Getting Started Skill safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Neo4j Getting Started Skill use?

Neo4j Getting Started Skill is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Neo4j Getting Started Skill use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 33k tokens, read only when the agent opens those files.

What are the alternatives to Neo4j Getting Started Skill?

Skills that share tags, products or a category with Neo4j Getting Started Skill: Jest Testing Patterns (ChrisWiles/claude-code-showcase, 6.1k stars), Java SDK E2E Test with Replay Snapshot (github/copilot-sdk, 11k stars), source-mssql E2E Test Harness (airbytehq/airbyte, 22k stars) and RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Neo4j Getting Started Skill?

neo4j-contrib (a GitHub organization) maintains it in neo4j-contrib/neo4j-skills, which has 114 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.

Source: neo4j-contrib/neo4j-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.