What problem does it solve? Provisioning Neo4j Aura cloud instances involves async lifecycle operations, one-time credential capture, OAuth2 token management, and tier/region selection that are easy to get wrong, leading to lost passwords, failed connections, and misconfigured CI/CD pipelines. ## Core Features & Use Cases - Instance Lifecycle Management: Create, pause, resume, resize, and delete AuraDB Free, Professional, Business Critical, and VDC instances via aura-cli or the Aura REST API. - Credential and Auth Handling: Set up OAuth2 client credentials, refresh 1-hour bearer tokens, and capture initial passwords that are never retrievable after creation. - CI/CD and Terraform Automation: Script provisioning in Python or declare instances with the neo4j/neo4j-aura Terraform provider, including async status polling until instances reach running state. - Use Case: A platform engineer needs an ephemeral Aura instance for every CI run. The Skill guides creating the instance via REST API, polling until status is running, writing credentials to a secrets vault, and tearing the instance down after tests. ## Quick Start Ask the agent to create a new AuraDB Professional instance in GCP europe-west1 and wait until it is running, saving the credentials to a .env file.
