What problem does it solve? LLMs frequently generate GRANT statements based on generic or MySQL-centric assumptions that break on MariaDB: implicit account creation rules, the renamed BINLOG MONITOR privilege, the SUPER privilege split, single-active-role semantics, and MariaDB-only privileges like DELETE HISTORY and READ_ONLY ADMIN. This Skill supplies the MariaDB-specific delta so generated privilege and role designs are correct. ## Core Features & Use Cases - Privilege catalog corrections: Documents MariaDB-only privileges (BINLOG MONITOR, DELETE HISTORY, SET USER, FEDERATED ADMIN, READ_ONLY ADMIN) and the SUPER privilege split so narrow privileges replace blanket SUPER grants. - Account creation and scope rules: Explains implicit user creation via GRANT with IDENTIFIED BY, the default NO_AUTO_CREATE_USER sql_mode, privilege scope levels (global, database, table, column, routine), and most-specific-pattern wildcard resolution. - Roles, proxy, and limits: Covers GRANT role TO user/role with WITH ADMIN OPTION, SET ROLE single-active-role semantics, GRANT PROXY requirements, resource limits, and REQUIRE TLS options. - Use Case: When asked to grant binlog monitoring access, the agent writes GRANT BINLOG MONITOR ON . instead of the legacy REPLICATION CLIENT alias, and avoids granting SUPER for tasks covered by narrower privileges. ## Quick Start Ask the AI to write or review a MariaDB GRANT statement, for example granting read-only access plus binlog monitoring to a new reporting user on MariaDB 11.8.