neo4j-aura-provisioning-skill
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/neo4j-aura 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.
80
92%
Does it follow best practices?
Impact
100%
1.78xAverage score across 1 eval scenario
High
Do not use without reviewing
Evaluation results
100%
44%AuraDB Infrastructure Provisioning for Microservice Launch
Terraform Aura provisioning with post-apply readiness polling
Official provider source
0%
100%
tenant_id field present
100%
100%
neo4j+s:// URI scheme
41%
100%
Companion polling script exists
100%
100%
Polls before marking ready
100%
100%
Token expiry handling
0%
100%
Correct .env variable names
20%
100%
.gitignore check
0%
100%
No hardcoded credentials
100%
100%
Cloud provider matches tier
100%
100%
Tier rationale documented
100%
100%
- Repository
- neo4j-contrib/neo4j-skills
- Commit
a3627d2
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.