CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

92

1.92x
Quality

88%

Does it follow best practices?

Impact

100%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable and well-structured skill with excellent workflow clarity, clear validation checkpoints, and fully executable code for CLI, REST, Python, and Terraform approaches. Its main weakness is length — the region tables, full Python script, and Terraform config inflate the token cost significantly and would be better served by progressive disclosure into bundle files. The content is accurate, well-organized, and covers edge cases thoroughly.

Suggestions

Move region code tables to a separate REGIONS.md reference file and link to it from the main skill, reducing ~40 lines of reference data from the primary context.

Extract the full Python CI/CD provisioning script and Terraform config into separate bundle files (e.g., examples/provision.py, examples/main.tf) referenced from the skill body.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good use of tables and code blocks, but the extensive region code tables (~60 rows), the full Python provisioning script, and the Terraform example make it quite long. Some of this reference data (region codes especially) would be better in a separate file. The content is factual and avoids explaining basics Claude knows, but the sheer volume could be tightened.

2 / 3

Actionability

Excellent actionability throughout — every operation has fully executable CLI commands, REST API curl commands, and Python code. The poll_status function is copy-paste ready, the Terraform config is complete, and the Python CI/CD script is fully runnable. Field tables, error tables, and rate limit info provide all details needed to act.

3 / 3

Workflow Clarity

The numbered step sequence (List Tenants → Create → Poll → Write .env → Lifecycle Ops) is clear and well-ordered. Critical validation checkpoints are explicit: polling until 'running' before proceeding, saving credentials immediately, checking .gitignore. The status lifecycle diagram and error recovery table provide feedback loops. Destructive operations (delete) have explicit warnings.

3 / 3

Progressive Disclosure

The content is well-structured with clear headers and sections, but it's a monolithic file with no bundle files to offload reference material. The region code tables, Python script, Terraform config, and error tables could all be separate referenced files. The WebFetch URLs section is a good touch for external references, but the skill itself would benefit from splitting into overview + reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an exemplary skill description that excels across all dimensions. It provides highly specific capabilities, rich natural trigger terms, explicit 'Use when' guidance, and outstanding distinctiveness through clear boundary definitions with redirects to related skills. The 'Does NOT' clauses are a particularly effective pattern for preventing skill conflicts in a large skill library.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: provisioning, managing, creating, pausing, resuming, resizing, deleting instances, downloading credentials, scripting CI/CD pipelines, polling async status, auth setup, credential lifecycle, instance type selection, region codes, and Python provisioning scripts.

3 / 3

Completeness

Clearly answers both 'what' (provisions and manages Neo4j Aura instances via CLI or REST API, with detailed sub-capabilities) and 'when' (explicit 'Use when' clause listing specific trigger scenarios). Additionally includes explicit boundary definitions with 'Does NOT' clauses pointing to alternative skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'Neo4j Aura', 'aura-cli', 'AuraDB', 'Free/Professional/Business Critical/VDC', 'credentials', 'CI/CD', 'Terraform', 'neo4j-aura provider', 'OAuth2', 'REST API', 'region codes', 'Python provisioning'. These are terms a user working with Neo4j Aura would naturally use.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive with a clear niche (Neo4j Aura provisioning/management). The explicit 'Does NOT' clauses with redirects to specific alternative skills (neo4j-cypher-skill, neo4j-gds-skill, neo4j-cli-tools-skill) actively prevent conflicts and make boundaries crystal clear.

3 / 3

Total

12

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
neo4j-contrib/neo4j-skills
Reviewed

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.