What problem does it solve? Slow Neo4j Cypher queries are hard to fix without understanding execution plans, operator behavior, and cardinality estimation. This Skill turns raw EXPLAIN/PROFILE output into concrete remediation steps so you can find missing indexes, bad operators, and stale statistics without guesswork. ## Core Features & Use Cases - Plan Interpretation: Explains EXPLAIN vs PROFILE, key metrics (dbHits, rows, estimatedRows, pageCacheHitRatio), and a full operator reference marking good and bad signals like AllNodesScan, CartesianProduct, and Eager. - Guided Diagnostic Runbook: A five-step workflow from baseline plan through index checks, index creation, post-fix profiling, and statistics replanning with db.prepareForReplanning and db.resampleIndex. - Fixes and Monitoring: Covers USING INDEX / USING SCAN / USING JOIN hints, slotted/pipelined/parallel runtime selection, and live query monitoring with SHOW QUERIES, SHOW TRANSACTIONS, and TERMINATE TRANSACTION. - Use Case: A MATCH query on Person nodes takes seconds instead of milliseconds. Run EXPLAIN, spot a NodeByLabelScan, create a RANGE index on the lookup property, then PROFILE twice to confirm dbHits dropped and NodeIndexSeek replaced the scan. ## Quick Start Ask the agent to diagnose why your slow Cypher query is underperforming by running EXPLAIN and interpreting the execution plan.