CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-graphql-skill

Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS security, auto-generated queries/mutations, OGM programmatic access, subscriptions via CDC, and Apollo Federation. Use when writing typeDefs, securing fields, or wiring Neo4j to Apollo Server. Does NOT handle raw Cypher outside resolvers — use neo4j-cypher-skill. Does NOT cover Spring Data Neo4j entity mapping — use neo4j-spring-data-skill.

78

1.29x
Quality

91%

Does it follow best practices?

Impact

100%

1.29x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 lean, highly actionable reference skill with executable code, version-aware guidance, and a properly split-out search-directives reference. Workflow sequencing and validation are solid but reference-oriented rather than offering explicit error-recovery loops; progressive disclosure is good though the main file is long.

Suggestions

Add an explicit validate→fix→retry loop for batch/large mutations (e.g., wrap createMovies in a batching pattern with a re-run on failure) to lift workflow_clarity above 4.

Consider moving the full per-directive syntax blocks (@relationship, @cypher, @authorization variants) into a references file the way @fulltext/@vector are handled, keeping SKILL.md as a tighter overview.

Add a one-line trigger note near the top of the body tying natural phrases ('GraphQL API for Neo4j', '.graphql typeDefs', 'Apollo Federation') to the When-to-Use list to broaden trigger-term coverage.

DimensionReasoningScore

Conciseness

Dense, code-first content with pointed inline comments ('columnName must exactly match the RETURN alias — mismatch returns null silently') and no padding explaining what GraphQL, Neo4j, or libraries are; version-sensitive material is isolated in 'Version Matrix' and 'v6 → v7 Breaking Changes' sections rather than scattered inline.

5 / 5

Actionability

Copy-paste ready executable code throughout — install commands, a complete minimal Apollo+Neo4j server, full directive syntax, security config, OGM CRUD, and subscriptions — plus a 'Common Errors' table mapping each failure to a concrete fix.

5 / 5

Workflow Clarity

Sequenced steps ('Step 1 — Install', 'Step 2 — Minimal Server Setup', Security Steps 1–3) with validation (assertIndexesAndConstraints wrapped in try/catch, a startup Checklist) and an error→fix table, but it is more reference-manual than linear workflow and lacks an explicit validate→fix→retry feedback loop for batch mutations.

4 / 5

Progressive Disclosure

Good structure with a clearly signaled one-level-deep reference ('Full syntax, generated query shapes, provider config: references/search-directives.md') that exists in the bundle, and clean section headers aid navigation, though the ~485-line body inlines substantial directive reference material that could be split further.

4 / 5

Total

18

/

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 what the skill does and when to use it, with excellent boundary guidance to avoid triggering for adjacent skills. Trigger-term coverage is good but slightly jargon-heavy and could include a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints()', '@cypher for custom resolvers', 'OGM programmatic access, subscriptions via CDC, and Apollo Federation' — giving comprehensive coverage with no vague filler.

5 / 5

Completeness

Explicitly answers both 'what' ('Build and configure a GraphQL API backed by Neo4j...') and 'when' ('Use when writing typeDefs, securing fields, or wiring Neo4j to Apollo Server') with concrete trigger phrases, and adds explicit out-of-scope boundary guidance.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'writing typeDefs', 'securing fields', 'wiring Neo4j to Apollo Server' are present, but coverage leans technical (OGM, CDC, JWKS) and omits common synonyms/extensions users might say such as '.graphql files' or 'graph schema'.

4 / 5

Distinctiveness Conflict Risk

A clear Neo4j-GraphQL niche with explicit de-confliction ('Does NOT handle raw Cypher outside resolvers — use neo4j-cypher-skill', 'Does NOT cover Spring Data Neo4j entity mapping — use neo4j-spring-data-skill') gives minimal conflict risk.

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

skill_md_line_count

SKILL.md is long (501 lines); consider splitting into references/ and linking

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.