Agent skill

Neo4j Aura Provisioning Skill

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

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

MITAuto-check: notesDevOps & Cloud

Install Neo4j Aura Provisioning Skill

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

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

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

At a glance

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

  • Works in 5 steps: List Tenants (Projects) → Create Instance → Poll Until RUNNING (CRITICAL — All Ops… → …
  • Deleting AuraDB Free/Professional/Business Critical/VDC instances
  • SKILL.md covers When to Use, When NOT to Use, Instance Tier Decision Table and Auth Setup, plus 13 more sections
  • Calls jq, curl and terraform; reaches api.neo4j.io and neo4j.com; needs AURA_CLIENT_SECRET and CLIENT_SECRET

What it does

Neo4j Aura Provisioning Skill is an agent skill from neo4j-contrib/neo4j-skills. Provisions and manages Neo4j Aura instances via CLI (aura-cli v1.7+) or REST API. Use when creating, pausing, resuming, resizing, or deleting AuraDB Free/Professional/Business Critical/VDC instances; downloading credentials; scripting CI/CD pipelines; polling async status; or using the Terraform neo4j-labs/neo4jaura provider. Covers auth setup (client credentials OAuth2), credential lifecycle (download once — never recoverable), instance type selection, region codes, and Python provisioning scripts. Does NOT…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `README.md`, `references/aura-agent.md` and `references/aura-monitoring.md`).

It sits in DevOps & Cloud, covering REST APIs, Infrastructure as code and OAuth and OpenID Connect. It works with Neo4j, Python and Terraform. The repository describes itself as: Neo4j Skills for Coding and other Agents including Cypher. The licence is MIT.

When your agent uses it

  • Deleting AuraDB Free/Professional/Business Critical/VDC instances
  • Downloading credentials
  • Scripting CI/CD pipelines
  • Polling async status

Example prompts

  • “Use the neo4j-aura-provisioning-skill skill to provision and manages Neo4j Aura instances via CLI (aura-cli v1.7+) or REST API”
  • “/neo4j-aura-provisioning-skill”

Requirements

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

Workflow steps

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

  1. List Tenants (Projects)
  2. Create Instance
  3. Poll Until RUNNING (CRITICAL — All Ops Are Async)
  4. Write .env and Verify
  5. Lifecycle Operations

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:

    • jq
    • curl
    • terraform

    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:

    • api.neo4j.io
    • 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
    • CLIENT_SECRET
    • NEO4J_PASSWORD

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

Context cost

Neo4j Aura Provisioning Skill loads about 3.7k tokens when it runs, and up to ~6.1k if it reads all its reference files. Until then it costs about 191 tokens; SKILL.md has 833 words of instructions outside code blocks.

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

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.

  • NoteRuns commands with sudoSKILL.md:54
    sudo mv aura-cli /usr/local/bin/
  • NoteMentions a .env fileSKILL.md:122
    # Extract for .env
  • NoteMentions a .env fileSKILL.md:202
    ## Step 4 — Write .env and Verify
  • NoteMentions a .env fileSKILL.md:207
    cat > .env <<EOF
  • NoteMentions a .env fileSKILL.md:215
    # Ensure .env never committed
  • NoteMentions a .env fileSKILL.md:216
    ^\.env$' .gitignore 2>/dev/null || echo '.env' >> .gitignore
  • NoteMentions a .env fileSKILL.md:448
    - Write initial credentials to `.env`; verify `.env` in `.gitignore` before proceeding
  • NoteMentions a .env fileSKILL.md:451
    - If `.env` absent: `python-dotenv` `load_dotenv()` auto-loads; do NOT prompt user unless loading fails
  • NoteMentions a .env fileSKILL.md:468
    - [ ] `.env` created with URI/user/password; `.env` in `.gitignore`
  • 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). 833 words, ~3,746 tokens.

Download SKILL.mdSave it as .claude/skills/neo4j-aura-provisioning-skill/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
neo4j-aura-provisioning-skill
description
Provisions and manages Neo4j Aura instances via CLI (aura-cli v1.7+) or REST API. Use when creating, pausing, resuming, resizing, or deleting AuraDB Free/Professional/Business Critical/VDC instances; downloading credentials; scripting CI/CD pipelines; polling async status; or using the Terraform neo4j-labs/neo4jaura provider. Covers auth setup (client credentials OAuth2), credential lifecycle (download once — never recoverable), instance type selection, region codes, and Python provisioning scripts. Does NOT handle Cypher queries — use neo4j-cypher-skill. Does NOT cover Graph Data Science algorithms — use neo4j-gds-skill or neo4j-aura-graph-analytics-skill. Does NOT cover neo4j-admin/cypher-shell — use neo4j-cli-tools-skill.
allowed-tools
Bash, WebFetch
version
1.0.5

When to Use

  • Creating an Aura instance (CLI, REST API, Python, Terraform)
  • Pausing, resuming, resizing, or deleting an instance
  • Downloading initial credentials from creation response
  • Polling instance status: creating → running
  • Setting up CI/CD provisioning or teardown pipelines
  • Choosing instance tier (Free vs Professional vs Business Critical vs VDC)

When NOT to Use

  • Cypher queries against running DB → neo4j-cypher-skill
  • GDS algorithms on Aura → neo4j-gds-skill (Pro with plugin) or neo4j-aura-graph-analytics-skill (serverless)
  • neo4j-admin / cypher-shell → neo4j-cli-tools-skill
  • Application driver setup → use a language driver skill (python, javascript, java, go, dotnet)

Instance Tier Decision Table

TierAPI type codeMemoryGDSReplicasUse when
AuraDB Freefree-db1 GB❌❌Dev/demo; ≤200k nodes/400k rels
AuraDB Professionalprofessional-db2–64 GBplugin available❌Production workloads
AuraDB Business Criticalbusiness-critical4–384 GBplugin available✅HA, multi-AZ, SLA
AuraDB VDCenterprise-dbcustom✅✅Dedicated infra, compliance
AuraDS Professionalprofessional-ds2–64 GB✅ built-in❌Data science / GDS
AuraDS Enterpriseenterprise-dscustom✅✅Enterprise GDS

AuraDB Free limits: 200k nodes, 400k rels; auto-pauses after 72 h inactivity; deleted if paused >30 days; no resize.


Auth Setup

CLI (aura-cli v1.7+)

Install (binary, not pip):

bash
# macOS
curl -L https://github.com/neo4j/aura-cli/releases/latest/download/aura-cli-darwin-amd64.tar.gz | tar xz
sudo mv aura-cli /usr/local/bin/
aura-cli -v          # verify

Add credentials (from console.neo4j.io → Account Settings → API Credentials):

bash
aura-cli credential add \
  --name "my-creds" \
  --client-id "$AURA_CLIENT_ID" \
  --client-secret "$AURA_CLIENT_SECRET"
aura-cli credential use --name "my-creds"

Verify:

bash
aura-cli instance list --output table
REST API — Get Bearer Token

Token endpoint: POST https://api.neo4j.io/oauth/token Token expires: 3600 s (1 h). On 403 → refresh token.

bash
TOKEN=$(curl -s --request POST 'https://api.neo4j.io/oauth/token' \
  --user "${AURA_CLIENT_ID}:${AURA_CLIENT_SECRET}" \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'grant_type=client_credentials' \
  | jq -r '.access_token')
echo "Token: ${TOKEN:0:20}..."

Use in all subsequent calls: --header "Authorization: Bearer $TOKEN"


Step 1 — List Tenants (Projects)

CLI:

bash
aura-cli tenants list --output table
# Copy TENANT_ID for create operations

REST:

bash
curl -s https://api.neo4j.io/v1/tenants \
  -H "Authorization: Bearer $TOKEN" | jq '.data[] | {id, name}'

Step 2 — Create Instance

CRITICAL: Capture output immediately. Initial password shown ONCE — never retrievable again. If lost: delete and recreate. Store aura-creds.json before doing anything else.

CLI
bash
aura-cli instance create \
  --name "my-instance" \
  --cloud-provider gcp \
  --region europe-west1 \
  --type professional-db \
  --tenant-id "$TENANT_ID" \
  --output json | tee aura-creds.json

# Extract for .env
INSTANCE_ID=$(jq -r '.id' aura-creds.json)
PASSWORD=$(jq -r '.password' aura-creds.json)
REST API (full create)
bash
RESPONSE=$(curl -s -X POST https://api.neo4j.io/v1/instances \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name":           "my-instance",
    "cloud_provider": "gcp",
    "region":         "europe-west1",
    "type":           "professional-db",
    "tenant_id":      "'"$TENANT_ID"'",
    "memory":         "4GB",
    "version":        "5"
  }')
echo "$RESPONSE" | tee aura-creds.json
INSTANCE_ID=$(echo "$RESPONSE" | jq -r '.data.id')
PASSWORD=$(echo "$RESPONSE"   | jq -r '.data.password')

Instance create request body fields:

FieldRequiredValues
name✅any string
cloud_provider✅gcp aws azure
region✅see region table
type✅see tier table
tenant_id✅from tenant list
memory✗1GB 2GB 4GB 8GB … 384GB
version✗5 (default)

Step 3 — Poll Until RUNNING (CRITICAL — All Ops Are Async)

ALL lifecycle operations (create, pause, resume, resize) are async. Do NOT attempt connection or next operation until status = running (or paused for pause op).

bash
poll_status() {
  local INSTANCE_ID=$1 TARGET=$2 MAX_WAIT=${3:-600}
  local ELAPSED=0 STATUS
  echo "Polling for status=$TARGET (max ${MAX_WAIT}s)..."
  while [ $ELAPSED -lt $MAX_WAIT ]; do
    STATUS=$(aura-cli instance get --instance-id "$INSTANCE_ID" --output json \
             | jq -r '.status' 2>/dev/null)
    echo "  [${ELAPSED}s] status=$STATUS"
    [ "$STATUS" = "$TARGET" ] && echo "Ready." && return 0
    [ "$STATUS" = "destroying" ] && echo "ERROR: instance is being destroyed" && return 1
    sleep 10; ELAPSED=$((ELAPSED + 10))
  done
  echo "TIMEOUT after ${MAX_WAIT}s — last status: $STATUS" && return 1
}

poll_status "$INSTANCE_ID" "running" 600

REST equivalent:

bash
while true; do
  STATUS=$(curl -s "https://api.neo4j.io/v1/instances/$INSTANCE_ID" \
    -H "Authorization: Bearer $TOKEN" | jq -r '.data.status')
  [ "$STATUS" = "running" ] && break
  sleep 10
done

Status lifecycle:

creating → running → pausing → paused → resuming → running
                  ↘ destroying → (gone)

Step 4 — Write .env and Verify

bash
CONNECTION_URI="neo4j+s://${INSTANCE_ID}.databases.neo4j.io"

cat > .env <<EOF
NEO4J_URI=${CONNECTION_URI}
NEO4J_USERNAME=neo4j
NEO4J_PASSWORD=${PASSWORD}
NEO4J_DATABASE=neo4j
AURA_INSTANCE_ID=${INSTANCE_ID}
EOF

# Ensure .env never committed
grep -q '^\.env$' .gitignore 2>/dev/null || echo '.env' >> .gitignore

# Verify connectivity
cypher-shell -a "$CONNECTION_URI" -u neo4j -p "$PASSWORD" "RETURN 'connected' AS status"

Step 5 — Lifecycle Operations

All operations require instance in the correct state. Wrong-state ops return 4xx error.

Pause

Required state: running

bash
aura-cli instance pause --instance-id "$INSTANCE_ID"
poll_status "$INSTANCE_ID" "paused" 600
Resume

Required state: paused

bash
aura-cli instance resume --instance-id "$INSTANCE_ID"
poll_status "$INSTANCE_ID" "running" 900   # resume can take longer
Resize (Professional+ only — NOT Free)

Required state: running; instance remains available during resize.

bash
# REST only — CLI resize not available in v1.7
curl -s -X PATCH "https://api.neo4j.io/v1/instances/$INSTANCE_ID" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"memory": "8GB"}'
poll_status "$INSTANCE_ID" "running" 600
# Cannot reduce below current usage level
Delete

IRREVERSIBLE. Export snapshots first if data needed.

bash
aura-cli instance delete --instance-id "$INSTANCE_ID"
# No poll needed — immediate

REST:

bash
curl -s -X DELETE "https://api.neo4j.io/v1/instances/$INSTANCE_ID" \
  -H "Authorization: Bearer $TOKEN"

Python CI/CD Provisioning Script

python
import os, time, requests

CLIENT_ID     = os.environ["AURA_CLIENT_ID"]
CLIENT_SECRET = os.environ["AURA_CLIENT_SECRET"]
BASE          = "https://api.neo4j.io/v1"

def get_token() -> str:
    r = requests.post(
        "https://api.neo4j.io/oauth/token",
        auth=(CLIENT_ID, CLIENT_SECRET),
        data={"grant_type": "client_credentials"},
    )
    r.raise_for_status()
    return r.json()["access_token"]

def auth_headers(token: str) -> dict:
    return {"Authorization": f"Bearer {token}", "Content-Type": "application/json"}

def create_instance(token: str, tenant_id: str, **kwargs) -> dict:
    payload = {"tenant_id": tenant_id, "version": "5", **kwargs}
    r = requests.post(f"{BASE}/instances", headers=auth_headers(token), json=payload)
    r.raise_for_status()
    return r.json()["data"]   # contains id, password, connection_url

def poll_status(token: str, instance_id: str, target: str, timeout: int = 600) -> None:
    deadline = time.time() + timeout
    while time.time() < deadline:
        r = requests.get(f"{BASE}/instances/{instance_id}", headers=auth_headers(token))
        r.raise_for_status()
        status = r.json()["data"]["status"]
        print(f"  status={status}")
        if status == target:
            return
        if status == "destroying":
            raise RuntimeError("Instance destroyed unexpectedly")
        time.sleep(10)
    raise TimeoutError(f"Instance {instance_id} did not reach '{target}' in {timeout}s")

# --- usage ---
token    = get_token()
instance = create_instance(
    token,
    tenant_id = os.environ["AURA_TENANT_ID"],
    name           = "ci-test-instance",
    cloud_provider = "aws",
    region         = "us-east-1",
    type           = "professional-db",
    memory         = "2GB",
)
# SAVE CREDENTIALS IMMEDIATELY — password never retrievable again
print(f"ID:       {instance['id']}")
print(f"URI:      neo4j+s://{instance['id']}.databases.neo4j.io")
print(f"Password: {instance['password']}")   # log to secure vault NOW

poll_status(token, instance["id"], "running", timeout=600)
print("Instance ready.")

Region Codes

AWS
Region codeLocation
us-east-1N. Virginia
us-east-2Ohio
us-west-2Oregon
eu-west-1Ireland
eu-west-3Paris
eu-central-1Frankfurt
ap-southeast-1Singapore
ap-southeast-2Sydney
ap-south-1Mumbai
sa-east-1São Paulo
GCP
Region codeLocation
europe-west1Belgium
europe-west3Frankfurt
europe-west4Netherlands
us-central1Iowa
us-east1S. Carolina
us-east4N. Virginia
asia-east1Taiwan
asia-northeast1Tokyo
asia-southeast1Singapore
australia-southeast1Sydney
Azure
Region codeLocation
eastusE. US
eastus2E. US 2
westeuropeNetherlands
northeuropeIreland
uksouthLondon
southeastasiaSingapore
brazilsouthBrazil
koreacentralKorea

Enterprise tiers (Business Critical, VDC) add 20+ additional regions per provider. Check console for full list. Free tier: GCP only; limited subset of regions.


Terraform Provider

hcl
terraform {
  required_providers {
    neo4jaura = {
      source  = "neo4j-labs/neo4jaura"
    }
  }
}

provider "neo4jaura" {
  client_id     = var.aura_client_id       # or AURA_CLIENT_ID env var
  client_secret = var.aura_client_secret   # or AURA_CLIENT_SECRET env var
}

resource "neo4jaura_instance" "db" {
  name           = "prod-db"
  type           = "professional-db"
  cloud_provider = "gcp"
  region         = "europe-west1"
  memory         = "4GB"
  project_id     = var.aura_project_id   # Terraform uses project_id (REST API: tenant_id)
}

output "neo4j_uri" {
  value     = neo4jaura_instance.db.connection_url
  sensitive = false
}
output "neo4j_password" {
  value     = neo4jaura_instance.db.password
  sensitive = true
}

After terraform apply: poll status before marking infra ready — Terraform resource creation returns when API call completes, not when DB is running.


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

Common Errors

ErrorCauseFix
403 Forbidden after workingToken expired (1 h TTL)Re-run get_token()
409 Conflict on createName already exists in tenantChange name or delete existing
422 on pauseInstance not runningCheck status; wait for ongoing op to finish
422 on resumeInstance not pausedCheck status
422 on resizeBelow current usageReduce data first; can't shrink below usage
Region not foundTier doesn't support that regionUse Free tier on GCP only; Pro/BC on all 3 clouds
Credentials lost after createPassword only returned at create timeDelete + recreate — no reset exists
429 Too Many RequestsRate limit hit (25 req/min Free, 125 req/min Pro+)Add time.sleep(2) between polling calls
instance list returns emptyWrong credential activeaura-cli credential use --name <name>

API Rate Limits

TierRequests/minute
Free / Pro Trial (no billing)25
Pro with billing, BC, VDC125

Poll interval: ≥10 s to stay within limits on Free; 5 s safe on Pro+. On Retry-After header in 5xx response: wait that many seconds before retry.


Security Rules

  • Write initial credentials to .env; verify .env in .gitignore before proceeding
  • Never print PASSWORD in CI logs — write to secrets vault (AWS Secrets Manager, GitHub secret, Vault)
  • Use from_env() / os.environ — never hardcode credentials
  • If .env absent: python-dotenv load_dotenv() auto-loads; do NOT prompt user unless loading fails

WebFetch — Current Docs

NeedURL
REST API spec (OpenAPI)https://neo4j.com/docs/aura/platform/api/specification/
CLI referencehttps://neo4j.com/docs/aura/aura-cli/
Region listhttps://neo4j.com/docs/aura/managing-instances/regions/
Auth detailshttps://neo4j.com/docs/aura/api/authentication/
Instance actionshttps://neo4j.com/docs/aura/managing-instances/instance-actions/

Checklist

  • .env created with URI/user/password; .env in .gitignore
  • Initial credentials saved to secure storage immediately after create
  • poll_status called after create — do NOT connect before status = running
  • poll_status called after pause/resume
  • Correct tier selected (Free for dev, Pro+ for production, BC for HA)
  • Region confirmed available for chosen tier and cloud provider
  • Tenant ID provided for all create/list operations (required in multi-tenant orgs)
  • Token refreshed if > 1 h old (or 403 received)
  • Delete confirmed by user — data loss is permanent, no recovery

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

  • SKILL.md
  • README.md
  • references/aura-agent.md
  • references/aura-monitoring.md
  • references/aura-tiers.md
  • references/data-importer.md

Open the folder on GitHubat commit bb30e1f

Compare with similar skills

Neo4j Aura Provisioning 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 Provisioning Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Neo4j Aura Provisioning Skill this skillneo4j-contrib/neo4j-skills114—~3.7kAutomated safety check: NotesMIT
Admingrafana/skills282—~1.5kAutomated safety check: PassApache-2.0
Devops Deploysickn33/agentic-awesome-skills47k2 repos~1.9kAutomated safety check: PassMIT
AWS GitHub Oidc Scoped Rolemizchi/skills360—~1.6kAutomated safety check: PassNone
Sca TrivyAgentSecOps/SecOpsAgentKit2202 repos~3.7kAutomated safety check: PassCustom licence
Google Cloud Storage Bucket Architectgoogle/skills21k—~2.6kAutomated safety check: PassApache-2.0

Similar skills

  • Admin

    grafana/skills

    Official

    Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning.

    282 GitHub stars~1.5k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Devops Deploy

    sickn33/agentic-awesome-skills

    DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.

    47k GitHub starsUsed in 2 repos~1.9k tokens
    DevOps & CloudAuto-check passed
  • OpenTofu/Terraform pattern for GitHub Actions OIDC trust with AWS IAM.

    360 GitHub stars~1.6k tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed
  • Sca Trivy

    AgentSecOps/SecOpsAgentKit

    Software Composition Analysis (SCA) and container vulnerability scanning using Aqua Trivy for identifying CVE vulnerabilities in dependencies, container images, IaC misconfigurations, and license…

    220 GitHub starsUsed in 2 repos~3.7k tokens
    SecurityAuto-check passed
  • Creates Cloud Storage on Google Cloud (also known colloquially as GCS) buckets.

    21k GitHub stars~2.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Datadog Data Source Generator

    DataDog/terraform-provider-datadog

    Official

    Generates a Datadog Terraform provider data source from an OpenAPI operation with tfgen and opens a review-ready GitHub PR with a risk scan and testing guide.

    468 GitHub stars~2.7k tokensUpdated yesterday
    DevOps & CloudAuto-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 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 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

Questions about Neo4j Aura Provisioning Skill

What does Neo4j Aura Provisioning Skill do?

Provisions and manages Neo4j Aura instances via CLI (aura-cli v1.7+) or REST API. Neo4j Aura Provisioning Skill is an agent skill from neo4j-contrib/neo4j-skills.7+) or REST API.

When should I use Neo4j Aura Provisioning Skill?

Neo4j Aura Provisioning Skill fits situations like: deleting AuraDB Free/Professional/Business Critical/VDC instances; downloading credentials; scripting CI/CD pipelines; polling async status.

How do I install Neo4j Aura Provisioning Skill in Claude Code?

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

How do I install Neo4j Aura Provisioning Skill in Codex?

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

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

What does Neo4j Aura Provisioning Skill need to run?

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

Does Neo4j Aura Provisioning Skill access the network?

SKILL.md names 3 domains. In commands or code: api.neo4j.io, 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 Provisioning Skill safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo; mentions a .env file; 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 Provisioning Skill use?

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

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

What are the alternatives to Neo4j Aura Provisioning Skill?

Skills that share tags, products or a category with Neo4j Aura Provisioning Skill: Admin (grafana/skills, 282 stars), Devops Deploy (sickn33/agentic-awesome-skills, 47k stars), AWS GitHub Oidc Scoped Role (mizchi/skills, 360 stars) and Sca Trivy (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

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