CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-query-tuning-skill

Diagnoses and fixes slow Neo4j Cypher queries by reading execution plans, identifying bad operators (AllNodesScan, CartesianProduct, Eager, NodeByLabelScan), and prescribing fixes (indexes, hints, query rewrites, runtime selection). Use when a query is slow, when EXPLAIN or PROFILE output needs interpretation, when dbHits or pageCacheHitRatio are poor, when cardinality estimation diverges from actuals, or when deciding between slotted/pipelined/parallel runtimes. Covers USING INDEX / USING SCAN / USING JOIN hints, db.stats.retrieve, SHOW QUERIES, SHOW TRANSACTIONS, TERMINATE TRANSACTION. Does NOT write new Cypher from scratch — use neo4j-cypher-skill. Does NOT cover GDS algorithm tuning — use neo4j-gds-skill. Does NOT cover index/constraint creation syntax details — use neo4j-cypher-skill references/indexes.md.

79

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

This is an exceptionally well-crafted skill that serves as a diagnostic runbook for Neo4j query performance. It combines dense reference tables (operators, metrics, runtimes) with a clear step-by-step workflow and concrete, executable examples for every common problem pattern. The content is highly token-efficient while remaining comprehensive, with appropriate progressive disclosure to external references for deeper detail.

DimensionReasoningScore

Conciseness

Every section earns its place — no explanations of what Neo4j or Cypher are, no padding. Tables are dense and scannable. The skill assumes Claude knows graph databases and focuses purely on diagnostic knowledge Claude wouldn't have memorized.

3 / 3

Actionability

Fully executable Cypher queries throughout, concrete curl commands for the Query API, specific index creation syntax, and copy-paste ready examples for every fix pattern. The operator reference table maps directly from symptom to fix.

3 / 3

Workflow Clarity

The 5-step diagnostic workflow is clearly sequenced with explicit validation checkpoints (wait for index ONLINE before measuring, PROFILE twice for cache warming, compare dbHits before/after). The checklist at the end provides a comprehensive verification loop. Feedback loops are present for stale statistics and Eager fixes.

3 / 3

Progressive Disclosure

The SKILL.md serves as a comprehensive but scannable overview with clear references to deeper content (references/plan-operators.md, references/stats-and-monitoring.md). Content is well-organized into logical sections with tables for quick lookup and detailed examples for complex scenarios. No bundle files were provided to verify reference accuracy, but the structure is sound.

3 / 3

Total

12

/

12

Passed

Description

100%

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

This is an exemplary skill description that excels across all dimensions. It provides highly specific capabilities with named operators and commands, includes comprehensive trigger terms that match natural user language, explicitly answers both what and when, and proactively delineates boundaries with related skills to prevent conflicts. The 'Does NOT' clauses with skill redirections are a particularly strong pattern for disambiguation.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: reading execution plans, identifying bad operators (with named examples like AllNodesScan, CartesianProduct), prescribing fixes (indexes, hints, query rewrites, runtime selection), and covers specific commands like USING INDEX, db.stats.retrieve, SHOW QUERIES, etc.

3 / 3

Completeness

Clearly answers both 'what' (diagnoses and fixes slow Neo4j Cypher queries by reading execution plans, identifying bad operators, prescribing fixes) and 'when' (explicit 'Use when...' clause listing five specific trigger scenarios). Additionally includes boundary definitions with 'Does NOT' clauses pointing to alternative skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'slow', 'Cypher queries', 'EXPLAIN', 'PROFILE', 'dbHits', 'pageCacheHitRatio', 'cardinality estimation', 'slotted/pipelined/parallel runtimes', 'Neo4j'. These are exactly the terms a user struggling with query performance would use.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive with a clear niche (Neo4j Cypher query performance tuning) and explicit boundary definitions that distinguish it from neo4j-cypher-skill and neo4j-gds-skill, making conflicts very unlikely.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.