What problem does it solve? Spark jobs that fail, retry, or suddenly crawl are hard to diagnose from driver stacktraces alone, and the wrong fix (like doubling executor memory) wastes cluster budget without addressing skew, shuffle, or memory root causes. ## Core Features & Use Cases - Pathology classification from the Spark UI: Reads the task-duration distribution in the failing stage to separate skew, shuffle-bound, memory, and retry/infrastructure failures before touching any code. - Targeted fix playbooks: Provides ordered fixes for skew (AQE skew joins, NULL/sentinel key handling, broadcast joins, salting), shuffle reduction (pushdown, partition tuning, bucketing), and OOM diagnosis (executor vs driver vs UDF memory). - Regression and verification discipline: Requires what-changed analysis for sudden slowdowns, before/after stage metrics at full production scale, and drift guards for data-shape root causes. - Use Case: A nightly enrichment job that ran in 45 minutes now takes 6 hours and OOMs. Use this Skill to identify a NULL join key affecting 210M rows from the task table, split those rows pre-join, enable AQE skew handling, and restore runtime to 38 minutes. ## Quick Start Diagnose why my Spark job is stuck at stage 12 with 199 of 200 tasks complete and fix the underlying bottleneck.