Conciseness

Lean and dense throughout — substitution tables, diff blocks, and exact commands with no explanations of concepts Claude already knows. Time-sensitive version information is organized as old→new pattern tables and a version-branched matrix, not free-floating dates. Not 4: there is no over-explanation to trim; every row carries migration-relevant facts.

Actionability

Fully executable guidance: copy-paste diffs for package renames (requirements.txt, pom.xml, go.mod, .csproj), exact replacement tables for every removed API, runnable scan commands in Step 1, per-language test commands, and a concrete curl template for EXPLAIN validation. Not 4: no pseudocode or vague steps; the common cases are covered with exact syntax.

Workflow Clarity

Clear sequence (Entry Criteria → Scan → Cypher migration → Driver migration → Compatibility matrix → Test) with explicit validation checkpoints: 'treat as ERROR — fix before proceeding' for deprecation warnings, 'EXPLAIN' every migrated query, and a final checklist. Not 3 (the batch-operation cap): this is a batch codebase migration and validation feedback loops are present, so the cap for missing validation does not apply.

Progressive Disclosure

Six one-level-deep references, each real, clearly signaled with per-file descriptions and 'Load on demand' framing; core substitution tables appropriately live in the body. Not 5: references/relational-to-graph.md exists in the bundle but is never linked from SKILL.md, leaving it undiscoverable — a minor organization gap.

Specificity

Lists multiple specific concrete actions with comprehensive coverage: 'package renames, removed APIs, version requirements, diff-ready fixes' plus named Cypher transformations ('id() → elementId()', 'PERIODIC COMMIT → CALL IN TRANSACTIONS') across five languages. Not 4: coverage spans both driver and Cypher migration with named replacements rather than having minor gaps.

Completeness

The 'what' is explicit and rich ('Migrates Neo4j driver code and Cypher queries from older versions (4.x, 5.x) to current'), and 'when' guidance exists via three explicit negative boundary clauses ('Does NOT write new Cypher queries — use neo4j-cypher-skill'), which function as explicit trigger routing. Not 5: there is no positive 'Use when upgrading…' trigger phrase; the 'when' is stated only negatively. Not 3: explicit boundary routing exceeds a merely implied 'when'.

Trigger Term Quality

Good natural keyword coverage — 'Neo4j', 'driver code', 'Cypher queries', 'Python, JavaScript/Node.js, Java, .NET, and Go', 'package renames', 'removed APIs'. Not 5: common synonyms users would say are missing — 'upgrade', 'deprecated', 'version bump' never appear, and no dependency-file terms (pom.xml, requirements.txt). Not 3: far more keyword coverage than a single generic phrase.

Distinctiveness Conflict Risk

Clear niche (Neo4j version migration) with three explicit redirects to sibling skills ('use neo4j-cypher-skill', 'use neo4j-cli-tools-skill', 'use neo4j-getting-started-skill'), which actively disambiguate overlapping triggers. Minimal conflict risk; not 4 because the boundaries are explicit rather than just topically distinct.