What problem does it solve? LLMs frequently emit MySQL-style plan-inspection syntax that fails on MariaDB, such as EXPLAIN ANALYZE or EXPLAIN FORMAT=TREE, or misuse ANALYZE on DML without realizing it actually executes the write. This Skill encodes MariaDB's actual grammar and runtime behavior for the EXPLAIN/ANALYZE statement family so generated SQL is valid and safe. ## Core Features & Use Cases - Correct statement selection: Distinguishes plain EXPLAIN (estimate only, never executes), standalone ANALYZE <statement> (executes for real, adds r_rows/r_filtered), and SHOW EXPLAIN/ANALYZE FOR <connection_id> for inspecting live queries. - Dialect delta table: Maps common mistakes to MariaDB forms — no EXPLAIN ANALYZE, no FORMAT=TREE, EXPLAIN EXTENDED required for the filtered column, and EXPLAIN tbl_name being a DESCRIBE synonym. - DML safety guidance: Warns that ANALYZE UPDATE/DELETE/INSERT actually commits writes, while EXPLAIN on DML is a true dry run. - Use Case: When asked to profile a slow query on MariaDB 11.8, produce ANALYZE FORMAT=JSON SELECT ... instead of the invalid EXPLAIN ANALYZE, or use SHOW EXPLAIN FOR <id> to inspect a query still running in another connection. ## Quick Start Ask the AI to write or review a MariaDB query-plan statement, for example: show me how to get real executed row counts for this SELECT on MariaDB.