What problem does it solve? Investigating MySQL or MariaDB issues during an incident requires many manual steps: discovering tables, checking schemas, running safe queries, and diagnosing replication lag or lock contention. This Skill packages those steps into ready-to-run scripts so an agent can inspect a database quickly without risking data modification. ## Core Features & Use Cases - Schema-First Exploration: List tables with size and engine stats, then describe columns, indexes, and foreign keys before writing queries. - Safe Read-Only Queries: Execute SELECT, SHOW, EXPLAIN, and DESCRIBE statements with automatic LIMIT injection; DML/DDL and multi-statement queries are blocked. - Health Diagnostics: Check the processlist for long-running queries, inspect InnoDB engine status for deadlocks, detect lock contention, and assess replication lag with a health classification. - Use Case: During an incident where the application is slow, run the processlist script to find long-running queries, check InnoDB status for deadlocks, and inspect table locks to pinpoint the blocking transaction. ## Quick Start Ask the agent to list the tables in the MySQL database and check for any long-running queries or lock contention.