Skill community intermediate
SQL Query Plan Explainer
Translate an EXPLAIN plan into plain language and the one change worth making.
Reads EXPLAIN / EXPLAIN ANALYZE output and explains scans, joins, spills and estimated-vs-actual row skew, then proposes the single highest-impact change.
npx de-agent-platform add sql-query-plan-explainer At a glance
| What | Translate an EXPLAIN plan into plain language and the one change worth making. |
|---|---|
| Where | SQL · tech-sql · tech-postgres · tech-duckdb |
Learning objectives
- Read a plan bottom-up and name the expensive node
- Detect cardinality misestimation from stale statistics
- Decide between an index, a rewrite, or a stats refresh
Security scan
Last sweep 2026-10-24: 0 finding(s), 0 marked as examples.
Details
SQL Query Plan Explainer
Method
- Read bottom-up; the deepest node is the first data touched.
- Compare
rows(estimate) toactual rows. >10x off means stale stats. - Look for
Seq Scanon a large table that should use an index. - Look for
Sort/Hashspilling to disk (disk usagein the plan).
Output
One sentence per expensive node, then exactly one recommended change with the expected effect and a way to measure it.
Registry stats
| Verification | community · Sep 22, 2026 |
|---|---|
| Completeness | 100 |
| Trust multiplier | ×1 |
| Composite | 38.5 · adequate |
| Freshness | 32 days since last source check |
| Difficulty | intermediate |
| Version | 0.2.1 |
| License | Apache-2.0 |
| Security flags | 1 |
Did this solve your problem?
SQL Query Plan Explainer