CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-getting-started-skill

Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building a notebook or app, or running the full onboarding pipeline. Time budget ≤15 min autonomous, ≤90 min HITL. Does NOT cover Cypher query authoring — use neo4j-cypher-skill. Does NOT cover driver upgrades or Cypher migration — use neo4j-migration-skill. Does NOT cover CLI/admin tasks on an existing DB — use neo4j-cli-tools-skill.

85

2.67x
Quality

92%

Does it follow best practices?

Impact

83%

2.67x

Average score across 2 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

A well-orchestrated, highly actionable skill body with clear stage sequencing, explicit validation gates, and clean one-level-deep reference deferral. The only weakness is modest duplication between the README template and the final-summary block.

DimensionReasoningScore

Conciseness

Dense and operational with no concept re-explanation, but the README template and final-summary block duplicate much of the file listing, and the progress.md example is long; minor trimming is possible.

4 / 5

Actionability

Provides copy-paste-ready commands (grep resume, cypher-shell, venv/pip), exact per-stage completion conditions, and a concrete success-gates table — fully executable orchestration.

5 / 5

Workflow Clarity

Clear 8-stage sequence with explicit dependencies, per-stage 'Verify the completion condition', 'If a stage fails, recover' feedback loops, hard gates, and a final checklist.

5 / 5

Progressive Disclosure

The body is an overview that defers each stage to one-level-deep references/<stage>.md files (verified present), with clearly signaled per-stage reference paths and a capabilities/ subfolder for shared material.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong, specific description that clearly states capabilities, trigger conditions, and boundaries against sibling skills. It uses third person and avoids fluff, with only minor gaps in synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (provision Aura, generate synthetic data, build notebook/app, run onboarding pipeline) and enumerates all 8 stages, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (orchestrates an 8-stage zero-to-running-app pipeline) and 'when' ('Use when starting a new Neo4j project...'), plus explicit 'does NOT cover' boundaries.

5 / 5

Trigger Term Quality

Good natural-term coverage ('new Neo4j project from scratch', 'provisioning Aura', 'synthetic data', 'notebook or app', 'onboarding pipeline'), though a few common variations like 'graph database setup' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear Neo4j onboarding niche with explicit conflict-avoidance boundaries naming three sibling skills (cypher, migration, cli-tools), minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

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.