Agent skill

Neo4j Aura Graph Analytics Skill

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

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

MITAuto-check: notesDatabases

Install Neo4j Aura Graph Analytics Skill

skills CLI
$ npx skills add neo4j-contrib/neo4j-skills --skill neo4j-aura-graph-analytics-skill -a claude-code

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

GitHub CLI
$ gh skill install neo4j-contrib/neo4j-skills neo4j-aura-graph-analytics-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-aura-graph-analytics-skill .claude/skills/neo4j-aura-graph-analytics-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-aura-graph-analytics-skill
GitHub stars
114
Token cost
~4.6k tokens
SKILL.md length
1,080 words
Files
4 (incl. references)
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 8 steps: Authenticate → Estimate Memory → Create Session → …
  • AuraDB-connected
  • SKILL.md covers When to Use, When NOT to Use, Deployment Decision Table and Defaults, plus 6 more sections
  • Calls pip; reaches neo4j.com and github.com; needs AURA_CLIENT_SECRET and NEO4J_PASSWORD

What it does

Neo4j Aura Graph Analytics Skill is an agent skill from neo4j-contrib/neo4j-skills. Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, getorcreate, remote graph projection with gds.graph.project.cypher and gds.graph.project.remote, gds.graph.project.native, gds.graph.construct, graphdatascience client 2.0 session endpoints, async compute and gds.jobs, AuraDB Cypher API memory/sessionId projection, algorithms, write-back, and session lifecycle. Use for AuraDB-connected, self-managed Neo4j, or…

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/limitations.md` and `references/workflows.md`).

It sits in Databases, covering Data warehousing, DataFrames and Serverless. It works with Neo4j and Snowflake. The repository describes itself as: Neo4j Skills for Coding and other Agents including Cypher. The licence is MIT.

When your agent uses it

  • AuraDB-connected
  • Self-managed Neo4j
  • Standalone DataFrame/Spark session workloads

Example prompts

  • “/neo4j-aura-graph-analytics-skill”

Requirements

  • Python 3
  • A credential in AURA_CLIENT_SECRET
  • Pre-approved tools (allowed-tools): Bash, WebFetch

Workflow steps

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

  1. Authenticate
  2. Estimate Memory
  3. Create Session
  4. Project Graph
  5. Run Algorithms
  6. Async Job Polling
  7. Retrieve Results
  8. Write Back and Clean Up

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

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • neo4j.com
    • github.com

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

  • Credentials

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

    • AURA_CLIENT_SECRET
    • NEO4J_PASSWORD
    • CLIENT_SECRET

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

Context cost

Neo4j Aura Graph Analytics Skill loads about 4.6k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 208 tokens; SKILL.md has 1,080 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, WebFetch

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); files beside SKILL.md are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/neo4j-aura-graph-analytics-skill/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
neo4j-aura-graph-analytics-skill
description
Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, get_or_create, remote graph projection with gds.graph.project.cypher and gds.graph.project.remote, gds.graph.project.native, gds.graph.construct, graphdatascience client 2.0 session endpoints, async compute and gds.jobs, AuraDB Cypher API memory/sessionId projection, algorithms, write-back, and session lifecycle. Use for AuraDB-connected, self-managed Neo4j, or standalone DataFrame/Spark session workloads. Does NOT cover the embedded GDS plugin on Aura Pro or self-managed Neo4j — use neo4j-gds-skill. Does NOT handle Cypher authoring — use neo4j-cypher-skill. Does NOT cover Snowflake Graph Analytics — use neo4j-snowflake-graph-analytics-skill.
allowed-tools
Bash, WebFetch
version
1.0.11

When to Use

  • Running GDS algorithms in Aura Graph Analytics GDS Sessions
  • Creating GdsSessions or using AuraGraphDataScience
  • Remote projecting connected Neo4j data with gds.graph.project.remote(...)
  • Using AuraDB Cypher API projection with { memory: ... } or { sessionId: ... }
  • Processing graph data from non-Neo4j sources (Pandas, Spark, CSV)
  • On-demand / pipeline workloads — ephemeral sessions, pay per session-minute
  • Full isolation from the live database during analytics

When NOT to Use

  • Aura Pro with embedded GDS plugin → neo4j-gds-skill
  • Self-managed Neo4j with embedded GDS plugin → neo4j-gds-skill
  • Writing Cypher queries → neo4j-cypher-skill
  • Snowflake Graph Analytics → neo4j-snowflake-graph-analytics-skill

Deployment Decision Table

DeploymentUse
AuraDB Freethis skill — max m_2GB, 1 concurrent session, unbilled
Aura Pro + Graph Analytics plugin enabled (lightweight exploration, shared resources)neo4j-gds-skill
Aura Pro / Pro Trial + session (isolated compute)this skill — up to 128 GB (Pro) / 8 GB (Pro Trial), 100 / 3 concurrent sessions
AuraDB + Python client sessionsthis skill
AuraDB + Cypher APIthis skill for AGA-specific projection/session notes; neo4j-cypher-skill for query authoring
Self-managed Neo4j + AGA sessionthis skill
Self-managed Neo4j + embedded pluginneo4j-gds-skill
Non-Neo4j data (Pandas, Spark)this skill (standalone mode)

Defaults

  • graphdatascience >= 2.0 required; >= 2.1 recommended
  • 2.0 endpoints: no v2 prefix — gds.page_rank.*, gds.graph.node_properties.*, gds.graph.construct(...)
  • Use snake_case parameters end-to-end
  • Call gds.verify_connectivity() after session creation — verifies session and, if attached, the source DB
  • Estimate memory before large sessions
  • Set TTL; default 1h idle, max 7d (hard 7-day lifetime cap)
  • Close session when done: gds.delete() or sessions.delete(session_name=...) stops billing
  • Use AuraAPICredentials.from_env() and DbmsConnectionInfo.from_env() — never hardcode credentials

Installation

bash
pip install "graphdatascience>=2.1"     # 2.1 is the current stable release

2.0 / 2.1 require: Python >= 3.10, neo4j driver 5.26–7.0, pandas 2–3, pyarrow 21–25, numpy <3.

Client 1.x (legacy)

2.0 renamed/reorganized the client. Pinned to 1.22 (graphdatascience<2)? Map:

1.x2.0
gds.v2.<endpoint>gds.<endpoint> — v2 prefix gone; untyped 1.x endpoints removed
gds.graph.project(graph_name, query) (remote)gds.graph.project.cypher(graph_name, query)
gds.graph.project_native(...)gds.graph.project.native(...)
GraphV2 / ModelV2Graph / Model — from graphdatascience import Graph
Graph.drop(failIfMissing=) / Model.drop(failIfMissing=)fail_if_missing=
gds.v2.verify_session_connectivity() / gds.v2.verify_db_connectivity()gds.verify_connectivity() — existed in 1.x too; v2 namespace gone
run_cypher(..., retryable=)removed — always retries
gds.graph.project.cypher(database=...)removed — gds.set_database(...) before projecting
gds.graph.node_labels.mutate(write_concurrency=, job_id=)parameters removed
ArrowEndpointVersion.from_arrow_infocheck_version_compatibility

Migration guide: Neo4j GDS Python client 2.0 migration

2.0 additions: GdsSessions.estimate(algorithms=[...]) per-algorithm memory; GdsSessions.get_or_create(show_progress=...); keyword-only GdsSessions.delete(session_name=|session_id=) returns False when nothing deleted; overwrite=True on gds.graph.project / generate / construct / filter / sample drops a same-named graph first; gds.graph.drop(...) accepts multiple graphs → list[GraphInfo].

2.1 additions: gds.run_cypher(query, auto_commit=True) for CALL { … } IN TRANSACTIONS (2.0 default retryable transaction rejects it); gds.db_driver() → session client's managed neo4j.Driver (closed by gds.close()); mode="READ"/"WRITE" strings accepted for QueryMode.


Key Patterns

Step 1 — Authenticate
python
from graphdatascience.session import AuraAPICredentials, GdsSessions

sessions = GdsSessions(api_credentials=AuraAPICredentials.from_env())
# Reads: AURA_CLIENT_ID, AURA_CLIENT_SECRET, AURA_PROJECT_ID (optional)
# Create API credentials in Aura Console → Account → API credentials

Member of multiple projects or organizations: set AURA_PROJECT_ID or pass project_id= — 2.1 checks organizations first when deriving the default project.

Step 2 — Estimate Memory
python
from graphdatascience.session import AlgorithmCategory, SessionMemory

# Per-algorithm + config — preferred
memory = sessions.estimate(
    node_count=1_000_000,
    relationship_count=5_000_000,
    algorithms=["wcc", "louvain", "fast_rp"],
)
# or with config:
memory = sessions.estimate(
    node_count=1_000_000,
    relationship_count=5_000_000,
    algorithms={"fast_rp": {"embedding_dimension": 128}},
)
# Coarse category estimate — 1.x style, still available
memory = sessions.estimate(
    node_count=1_000_000,
    relationship_count=5_000_000,
    algorithm_categories=[
        AlgorithmCategory.CENTRALITY,
        AlgorithmCategory.NODE_EMBEDDING,
        AlgorithmCategory.COMMUNITY_DETECTION,
    ],
)
# Returns SessionMemory tier, e.g. SessionMemory.m_8GB
# Fixed tiers: m_2GB … m_512GB — see references/limitations.md
Step 3 — Create Session

Mode A — AuraDB connected:

python
from graphdatascience.session import DbmsConnectionInfo, SessionMemory, CloudLocation
from datetime import timedelta

# Reads: AURA_INSTANCEID (takes precedence) or NEO4J_URI, plus NEO4J_USERNAME,
# NEO4J_PASSWORD, NEO4J_DATABASE
db_connection = DbmsConnectionInfo.from_env()
# Explicit: DbmsConnectionInfo(aura_instance_id=..., username=..., password=...)

gds = sessions.get_or_create(
    session_name="my-analysis",
    memory=memory,
    db_connection=db_connection,
    ttl=timedelta(hours=2),
)
gds.verify_connectivity()

Mode B — Self-managed Neo4j:

python
# Same from_env() — set NEO4J_URI (e.g. "bolt://my-server:7687"), no AURA_INSTANCEID
gds = sessions.get_or_create(
    session_name="my-analysis-sm",
    memory=SessionMemory.m_8GB,
    db_connection=DbmsConnectionInfo.from_env(),
    ttl=timedelta(hours=2),
    cloud_location=CloudLocation("gcp", "europe-west1"),
)
gds.verify_connectivity()

Mode C — Standalone (no Neo4j DB):

python
gds = sessions.get_or_create(
    session_name="my-standalone",
    memory=SessionMemory.m_4GB,
    ttl=timedelta(hours=1),
    cloud_location=CloudLocation("gcp", "europe-west1"),
)
gds.verify_connectivity()

get_or_create() is idempotent; reconnects to existing session by name.

Step 4 — Project Graph

From connected Neo4j (remote projection):

python
query = """
    CALL () {
        MATCH (p:Person)
        OPTIONAL MATCH (p)-[r:KNOWS]->(p2:Person)
        RETURN p AS source, r AS rel, p2 AS target,
               p {.age, .score} AS sourceNodeProperties,
               p2 {.age, .score} AS targetNodeProperties
    }
    RETURN gds.graph.project.remote(source, target, {
        sourceNodeLabels:     labels(source),
        targetNodeLabels:     labels(target),
        sourceNodeProperties: sourceNodeProperties,
        targetNodeProperties: targetNodeProperties,
        relationshipType:     type(rel)
    })
"""

G, result = gds.graph.project.cypher(
    graph_name="my-graph",
    query=query,
    undirected_relationship_types=["KNOWS"],
)
print(f"Projected {G.node_count()} nodes, {G.relationship_count()} relationships")

CALL () { ... } required for multi-pattern MATCH. Use UNION inside CALL for multiple labels/rel types. Remote query must use gds.graph.project.remote(...); graph name goes to gds.graph.project.cypher(...), not the query. Query containing gds.graph.project without .remote is auto-rewritten with a warning. undirectedRelationshipTypes / inverseIndexedRelationshipTypes inside the query → ValueError — pass as method args. Only numeric node properties can be projected into a session; fetch string properties via db_node_properties when streaming. Standalone sessions cannot remote-project — ValueError: Remote projection is only supported for attached Sessions. 1.x fallback: gds.graph.project(graph_name=..., query=...).

Native remote projection (no Cypher query) — gds.graph.project.native(...) projects from the attached DB by label/type filter:

python
G, result = gds.graph.project.native(
    "my-graph",
    ["Person"],                              # node_label_filter
    ["KNOWS"],                               # relationship_type_filter
    node_properties=["age", "score"],
    undirected_relationship_types=["KNOWS"],
)

Attached sessions only. Use project.native for label/type-filtered projections; use project.cypher for transformations, computed properties, or UNION heterogeneous patterns.

AuraDB Cypher API projection:

cypher
CYPHER runtime=parallel
MATCH (source)
OPTIONAL MATCH (source)-->(target)
RETURN gds.graph.project(
  'my-graph',
  source,
  target,
  {},
  { memory: '2GB' }
)

Existing explicit session:

cypher
CYPHER runtime=parallel
MATCH (source)
OPTIONAL MATCH (source)-->(target)
RETURN gds.graph.project(
  'my-graph',
  source,
  target,
  {},
  { sessionId: '00000000-11111111' }
)

Cypher API uses gds.graph.project(...), not gds.graph.project.remote(...). Put memory, ttl, sessionId, batchSize in fifth config argument.

Session management via Cypher API:

cypher
CALL gds.session.getOrCreate('test-session', '2GB', duration({minutes: 30}))
YIELD id, name, status
RETURN id, name, status

CALL gds.session.list()
YIELD id, name, status, memory
RETURN id, name, status, memory

Implicit Cypher API sessions delete when all projected graphs in session are dropped.

From Pandas DataFrames (standalone mode):

python
import pandas as pd

nodes_df = pd.DataFrame([
    {"nodeId": 0, "labels": "Person", "age": 30},
    {"nodeId": 1, "labels": "Person", "age": 25},
])
rels_df = pd.DataFrame([
    {"sourceNodeId": 0, "targetNodeId": 1, "relationshipType": "KNOWS"},
])

G = gds.graph.construct("my-graph", [nodes_df], [rels_df])

Required columns — nodes: nodeId (int), labels (str). Relationships: sourceNodeId, targetNodeId, relationshipType. Drop string node properties before construct() — sessions accept numeric properties only.

Step 5 — Run Algorithms
python
# Mutate — chain results without writing to DB
gds.page_rank.mutate(G, mutate_property="pagerank", damping_factor=0.85)
gds.fast_rp.mutate(G,
    mutate_property="embedding",
    embedding_dimension=128,
    feature_properties=["pagerank"],
    random_seed=42,
)

# Stream — inspect results as DataFrame
df = gds.page_rank.stream(G)
print(df.sort_values("score", ascending=False).head(10))

# Write — persist to connected Neo4j DB (connected modes only)
gds.louvain.write(G, write_property="community")

ML pipelines: gds.pipeline.node_classification / link_prediction / node_regression — the only API in 2.0. 1.x fallback: gds.v2.page_rank.mutate(...); untyped 1.x endpoints like gds.pageRank.mutate(...) are gone in 2.0. Plugin algorithm reference → neo4j-gds-skill; AGA limitations differ.

Show full SKILL.md (422 more words)Show less
Step 6 — Async Job Polling

Long-running algorithms — non-blocking compute() returns a JobHandle:

python
import time

job = gds.page_rank.compute(G, mutate_property="pagerank")
while not job.done():
    time.sleep(5)
    print(f"Job status: {job.status()}")
if job.status() != "RUNNING_DONE":
    raise RuntimeError(f"Algorithm job failed: {job.status()}")
result = job.result(wait=False)   # raises JobNotFinishedError if not done

Handle methods: .job_id(), .status(), .done(), .wait(*, termination_flag=None), .cancel(), .summary(...), .result(wait=False). Async projections return ProjectionJobHandle (gds.graph.project.native_async(...), cypher_async(...)); write-backs yield WriteJobHandle. List/recover jobs:

python
gds.jobs.list()                     # JobInfo per job: job_id, name
handle = gds.jobs.get(G, job_id)    # concrete handle type for the job
Step 7 — Retrieve Results
python
# Stream node properties
result_df = gds.graph.node_properties.stream(
    G,
    node_properties=["pagerank", "embedding"],
    db_node_properties=["name"],   # connected modes only — fetches string props from DB
)
result_df.head(10)

Standalone mode: no db_node_properties; join source DataFrame:

python
result_df = gds.graph.node_properties.stream(G, ["pagerank"])
result_df.merge(nodes_df[["nodeId", "name"]], how="left")
Step 8 — Write Back and Clean Up
python
# Write node properties to connected Neo4j
gds.graph.node_properties.write(G, ["pagerank", "embedding"])

# Write relationship properties
gds.graph.relationships.write(G, "SIMILAR", ["score"])

# Query connected DB from session
gds.run_cypher("MATCH (n:Person) RETURN count(n)")

# Drop projected graph
gds.graph.drop(G)

# Delete session
sessions.delete(session_name="my-analysis")
# or: gds.delete()

Write before delete; unwritten results lost when session closes.

Session Management
python
# List active sessions
from pandas import DataFrame
DataFrame(sessions.list())

# Reconnect to existing session
gds = sessions.get_or_create(session_name="my-analysis", memory=..., db_connection=...)

Common Errors

ErrorCauseFix
AuthenticationError / 401Wrong CLIENT_ID/CLIENT_SECRETRegenerate in Aura Console → Account → API credentials
RuntimeError getting an already-expired sessionTTL exceededsessions.list() to check; recreate session
SessionNotFoundErrorSession expired (TTL exceeded) or name typosessions.list() to check; recreate session
GraphNotFoundErrorProjection dropped or session reconnected without re-projectingRe-run gds.graph.project.cypher() or gds.graph.construct()
ValueError: Remote projection is only supported for attached Sessions.Standalone session cannot remote-projectUse gds.graph.construct(...) from DataFrames instead
NotAvailableInStandaloneSessionsFeature needs an attached DB (e.g. gds.topological_link_prediction, remote projection)Attach a DB or pick another algorithm
Algorithm job FAILEDMemory limit exceeded or unsupported algorithmIncrease SessionMemory; check NotAvailableOutsideAura for attached-only features
MemoryEstimationExceededGraph larger than estimatedRe-estimate with actual counts; pick next tier up
Results empty after session reconnectResults not written before session was closedAlways write/stream before gds.delete()
String node properties not supportedString column in nodes DataFrameDrop string columns before gds.graph.construct(); fetch strings later via db_node_properties
AGA not enabled for projectAGA feature not activatedEnable in Aura Console → project settings

References

Load on demand:

WebFetch

NeedURL
AGA Python client docshttps://neo4j.com/docs/graph-data-science-client/current/aura-graph-analytics/
AGA Cypher API docshttps://neo4j.com/docs/graph-data-science/current/aura-graph-analytics/cypher/
Client migration guide 1.x → 2.0https://neo4j.com/docs/graph-data-science-client/current/migration-from-1x/
AuraDB tutorial notebookhttps://github.com/neo4j/graph-data-science-client/blob/main/examples/graph-analytics-serverless.ipynb
GDS algorithm referencehttps://neo4j.com/docs/graph-data-science/current/algorithms/

Checklist

  • Aura API credentials created and set in environment (AURA_CLIENT_ID, AURA_CLIENT_SECRET)
  • Connected sessions: AURA_INSTANCEID or NEO4J_URI, plus NEO4J_USERNAME, NEO4J_PASSWORD set for DbmsConnectionInfo.from_env()
  • AGA feature enabled for Aura project (Aura Console → project settings)
  • Memory estimated before session creation (sessions.estimate(..., algorithms=[...]))
  • Cloud location chosen near data source
  • gds.verify_connectivity() called after session creation
  • Remote projection uses gds.graph.project.cypher(graph_name, query) with gds.graph.project.remote(...) inside query
  • Remote projection graph name passed to the endpoint, not the remote function
  • undirected_relationship_types passed as method args, never inside the query
  • AuraDB Cypher API projection uses fifth config map for memory or sessionId
  • Explicit Cypher API sessions use gds.session.getOrCreate(...); implicit sessions dropped with projected graph
  • TTL set to avoid unexpected costs on idle sessions
  • Async algorithm jobs polled until RUNNING_DONE before reading results
  • Results written back (connected modes) or streamed and persisted (standalone) before deletion
  • Session deleted when done (sessions.delete(session_name=...) or gds.delete())

© 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 3 other files (references) in neo4j-aura-graph-analytics-skill of neo4j-contrib/neo4j-skills.

  • SKILL.md
  • README.md
  • references/limitations.md
  • references/workflows.md

Open the folder on GitHubat commit bb30e1f

Compare with similar skills

Neo4j Aura Graph Analytics 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 Aura Graph Analytics Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Neo4j Aura Graph Analytics Skill this skillneo4j-contrib/neo4j-skills114—~4.6kAutomated safety check: NotesMIT
Snowflake Snowpark DbtMindrally/skills271—~2.5kAutomated safety check: PassApache-2.0
Analyzing Dataastronomer/agents451—~1.3kAutomated safety check: PassApache-2.0
Expensive Snowflake Query FinderAltimateAI/data-engineering-skills128—~662Automated safety check: PassMIT
Managing Databasesrileyhilliard/claude-essentials130—~1.6kAutomated safety check: PassMIT
Snowflake Developmentsickn33/agentic-awesome-skills47k2 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Snowflake Snowpark Dbt

    Mindrally/skills

    Best practices for Snowpark Python (DataFrames, UDFs, UDTFs, stored procedures) and dbt with the dbt-snowflake adapter.

    271 GitHub stars~2.5k tokensUpdated 2 days ago
    Data & AnalyticsAuto-check passed
  • Analyzing Data

    astronomer/agents

    Queries the data warehouse with SQL and answers business questions about data.

    451 GitHub stars~1.3k tokensUpdated 3 days ago
    DatabasesAuto-check passed
  • Expensive Snowflake Query Finder

    AltimateAI/data-engineering-skills

    Ranks the costliest, slowest or heaviest-scanning Snowflake queries from query history and suggests how to optimize them.

    128 GitHub stars~662 tokensUpdated 3 days ago
    DatabasesAuto-check passed
  • Managing Databases

    rileyhilliard/claude-essentials

    Guides database architecture for PostgreSQL, DuckDB, Parquet, PGVector, and Neo4j.

    130 GitHub stars~1.6k tokensUpdated 1 mo ago
    DatabasesAuto-check passed
  • Snowflake Development

    sickn33/agentic-awesome-skills

    Comprehensive Snowflake development assistant covering SQL best practices, data pipeline design (Dynamic Tables, Streams, Tasks, Snowpipe), Cortex AI functions, Cortex Agents, Snowpark Python, dbt…

    47k GitHub starsUsed in 2 repos~2.1k tokens
    DatabasesAuto-check passed
  • Snowflake Development

    alirezarezvani/claude-skills

    A skill your agent uses when writing Snowflake SQL, building data pipelines with Dynamic Tables or Streams/Tasks, using Cortex AI functions, creating Cortex Agents, writing Snowpark Python…

    28k GitHub stars~3.2k tokensUpdated 1 mo ago
    DatabasesAuto-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 Getting Started Skill

    neo4j-contrib/neo4j-skills

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

    114 GitHub stars~4.3k tokensUpdated yesterday
    Auto-check: warnings
  • 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

Questions about Neo4j Aura Graph Analytics Skill

What does Neo4j Aura Graph Analytics Skill do?

Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, getorcreate, remote graph projection with…. Neo4j Aura Graph Analytics Skill is an agent skill from neo4j-contrib/neo4j-skills.jobs, AuraDB Cypher API memory/sessionId projection, algorithms, write-back, and session lifecycle.

When should I use Neo4j Aura Graph Analytics Skill?

Neo4j Aura Graph Analytics Skill fits situations like: auraDB-connected; self-managed Neo4j; standalone DataFrame/Spark session workloads.

How do I install Neo4j Aura Graph Analytics Skill in Claude Code?

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

How do I install Neo4j Aura Graph Analytics Skill in Codex?

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

Can I use Neo4j Aura Graph Analytics 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-aura-graph-analytics-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-aura-graph-analytics-skill, .gemini/skills/neo4j-aura-graph-analytics-skill, .github/skills/neo4j-aura-graph-analytics-skill and .opencode/skills/neo4j-aura-graph-analytics-skill in your project.

What does Neo4j Aura Graph Analytics Skill need to run?

Going by SKILL.md and its folder, Neo4j Aura Graph Analytics Skill needs the command-line tools its instructions call (pip) and credentials named AURA_CLIENT_SECRET, NEO4J_PASSWORD and CLIENT_SECRET. Our summary lists: Python 3; A credential in AURA_CLIENT_SECRET. Its frontmatter pre-approves these tools: Bash, WebFetch.

Does Neo4j Aura Graph Analytics Skill access the network?

SKILL.md names 2 domains. In commands or code: neo4j.com and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Neo4j Aura Graph Analytics Skill safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Neo4j Aura Graph Analytics Skill use?

Neo4j Aura Graph Analytics 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 Aura Graph Analytics Skill use?

About 4.6k tokens (SKILL.md is roughly 19k 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 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Neo4j Aura Graph Analytics Skill?

Skills that share tags, products or a category with Neo4j Aura Graph Analytics Skill: Snowflake Snowpark Dbt (Mindrally/skills, 271 stars), Analyzing Data (astronomer/agents, 451 stars), Expensive Snowflake Query Finder (AltimateAI/data-engineering-skills, 128 stars) and Managing Databases (rileyhilliard/claude-essentials, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Neo4j Aura Graph Analytics 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.