Conciseness

The body is dense and terse — tables, short bullets, and version-gated gotchas Claude would not know (e.g., "**`Z` ≠ UTC in Neo4j**", "`toInteger(null)` throws") with no padding explaining known concepts. It matches the level-4 anchor (efficient with minor instances that could be trimmed): the DISJOINT BY, UUID type, and spatial sections carry reference-grade detail that duplicates what the reference files already cover, and the inline trap table partially duplicates references/syntax-traps.md.

Actionability

Nearly every section gives copy-paste-ready Cypher: concrete MERGE/WITH/subquery/bulk-load examples, an exact curl command for the Query API v2, specific index/constraint DDL, and precise validation commands ("EXPLAIN before any write", "PROFILE to measure db hits; check for AllNodesScan, CartesianProduct, Eager"). This matches the level-5 anchor (fully executable, common cases covered); the one non-executable element (the schema sketch) is explicitly and appropriately justified ("Never fill guessed names").

Workflow Clarity

The multi-step process is explicitly sequenced with validation checkpoints: the Pre-flight decision table, the Schema-First Protocol priority order, the 4-step validation workflow (EXPLAIN → LIMIT 1 test → verify write half as RETURN → PROFILE), the write execution gate requiring user confirmation, plus a Failure Recovery section with fix-and-retry feedback loops and a closing checklist. This matches the level-5 anchor, including the database-operations feedback-loop requirement.

Progressive Disclosure

Eight real, one-level-deep reference files are well signaled — each with a descriptive entry in the References section and point-of-use links ("Full trap table → references/syntax-traps.md") — plus three real scripts. This is good structure matching the level-4 anchor; it falls short of level 5 because the ~430-line body inlines substantial detail (QPE patterns, DISJOINT BY, UUID, spatial, aggregation rules) that mirrors and partially duplicates the reference files, so the split between overview and detail is imperfect.

Specificity

"Generates, optimizes, and validates Cypher 25 queries" lists three concrete actions, and "Covers MATCH, MERGE, CREATE, WITH, RETURN, CALL, UNWIND, FOREACH, LOAD CSV, SEARCH, expressions, functions, indexes, and subqueries" enumerates comprehensive capability coverage. This matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage), not level 4, since there are no meaningful coverage gaps in the actions named.

Completeness

The "what" is explicit ("Generates, optimizes, and validates Cypher 25 queries for Neo4j 2025.x and 2026.x") and the "when" is explicit with concrete triggers ("Use when writing new Cypher queries, optimizing slow queries, ..."). This clearly matches the level-5 anchor (both what and when with concrete trigger phrases), not level 4, since the when-clause is fully explicit rather than merely serviceable.

Trigger Term Quality

"Use when writing new Cypher queries, optimizing slow queries, graph pattern matching, vector or fulltext search, subqueries, or batch writes" covers the natural phrasings a user would say for this need, including variations like "optimizing slow queries". This matches the level-5 anchor (comprehensive natural-term coverage with variations); there is no file-extension equivalent for a query-generation skill, and no commonly used trigger term for Cypher work is missing.

Distinctiveness Conflict Risk

Two explicit disambiguation fences are present ("Does NOT handle driver migration or API changes — use neo4j-migration-skill", "Does NOT cover DB administration or server ops — use neo4j-cli-tools-skill"), giving a mostly distinct niche. However, the "vector or fulltext search" trigger overlaps the sibling neo4j-vector-index-skill (which the body's When-NOT-to-Use section defers hybrid search to) and the description adds no boundary note for it, matching the level-4 anchor (minor overlap risk with a closely related skill) rather than level 5.