neo4j-query-tuning-skill

What problem does it solve?

Neo4j users get stuck with slow or unpredictable Cypher queries without knowing which plan operators, missing indexes, or runtime choices are causing the slowness.

Core Features & Use Cases

• Plan interpretation (EXPLAIN vs PROFILE): Decide when to use each and read key metrics like dbHits, estimatedRows, and pageCacheHitRatio to validate whether the plan matches reality.
• Operator diagnostics with targeted fixes: Identify bad signals such as AllNodesScan, NodeByLabelScan, CartesianProduct, and Eager, then prescribe concrete remedies like indexes, query rewrites, hints, and LIMIT placement.
• Planner accuracy & monitoring workflow: Detect stale cardinality estimation and trigger replanning or index resampling, while using SHOW QUERIES / SHOW TRANSACTIONS to diagnose and terminate problematic live queries.

Use Case: When a query is slow and PROFILE shows high dbHits and a plan containing a scan operator, use this Skill to pinpoint the exact operator and apply the appropriate index/hint/runtime strategy to reduce IO and improve selectivity.

Quick Start

Ask the Skill to analyze the output of PROFILE for your slow Cypher query and propose the smallest targeted changes to eliminate the specific bad plan operators it identifies.