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.

90

1.10x
Quality

87%

Does it follow best practices?

Impact

94%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is a well-organized, executable reference with strong actionability and clean progressive disclosure via one real reference file. Its only gap is the absence of an explicit validate→fix→retry loop for destructive/batch database and auth operations, which keeps workflow clarity at 4.

Suggestions

Add an explicit validate→fix→retry feedback loop around destructive or batch operations (e.g. nested createMovies mutations, assertIndexesAndConstraints on startup) so workflow_clarity can reach 5.

Tighten the version matrix and security-fix tables to the minimal actionable rows to trim token weight.

Surface the CDC FULL-mode prerequisite as an explicit validation checkpoint before enabling features.subscriptions rather than only in the Checklist.

DimensionReasoningScore

Conciseness

Body is mostly lean and assumes competence (no 'what is GraphQL' padding), with inline comments earning their place; minor tightening possible in the version/security tables and some directive sections, keeping it above 3 but not a pristine 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code for server setup, directives, auth, OGM, and subscriptions, plus a Common Errors table mapping concrete error strings to fixes covering the common cases.

5 / 5

Workflow Clarity

Sequenced install → server setup → directives → security steps with a startup validation checkpoint (assertIndexesAndConstraints wrapped in try/catch) and an end Checklist; not a 5 because destructive/batch database and auth operations lack an explicit validate-then-retry feedback loop beyond the error table.

4 / 5

Progressive Disclosure

Clear overview structure with a single well-signaled one-level-deep reference (references/search-directives.md, which exists) for @fulltext/@vector detail; all other content appropriately inline and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

90%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.

The description is specific, complete, and clearly scoped with explicit 'Use when' triggers and negative-boundary pointers to sibling skills. It is slightly dense rather than sparse on natural-language trigger synonyms, but excels on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities (constructor, getSchema(), assertIndexesAndConstraints(), @node/@relationship/@cypher/@authorization directives, OGM, subscriptions via CDC, Apollo Federation) with comprehensive coverage; not below 4 because it goes well beyond 'several specific actions' and into full feature enumeration.

5 / 5

Completeness

Explicitly answers both 'what' (build/configure a GraphQL API backed by Neo4j with listed capabilities) and 'when' ('Use when writing typeDefs, securing fields, or wiring Neo4j to Apollo Server'), plus negative boundaries; clearly matches the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'writing typeDefs', 'securing fields', 'wiring Neo4j to Apollo Server' and the directive names users would say, but lacks common synonyms/file extensions (e.g. 'schema', 'GraphQL API') beyond the core terms, so it sits above 3 but not at full 5 coverage.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (@neo4j/graphql) and two explicit de-scope clauses ('Does NOT handle raw Cypher — use neo4j-cypher-skill', 'Does NOT cover Spring Data Neo4j — use neo4j-spring-data-skill'), minimizing conflict with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.