What problem does it solve? LLMs frequently generate incorrect mariadb CLI commands based on outdated MySQL-era assumptions, such as expecting boxed output in batch mode, using the nonexistent sql_max_join_size variable, or assuming a latin1 default charset. This Skill provides the MariaDB-specific facts needed to write, generate, and review correct CLI invocations. ## Core Features & Use Cases - Batch vs. interactive behavior: Explains that piped input, -e, or --batch auto-switches to tab-separated output and disables the history file, with --table to force boxed output back. - Safety guardrails: Covers --safe-updates semantics, including that it sets max_join_size (no sql_ prefix) and blocks UPDATE/DELETE without a key-based WHERE or LIMIT. - Client-side commands and charset handling: Details DELIMITER for stored-routine bodies, \G vertical output, locale-based charset auto-detection, and the mysql symlink compatibility. - Use Case: When asked to write a migration script that runs mariadb appdb < migration.sql, the Skill ensures the agent accounts for batch-mode output, --force error handling, and correct password flag syntax (-pmypassword, not -p mypassword). ## Quick Start Ask the AI to write a shell command that runs a SQL migration file against a MariaDB database using the mariadb client with safe-updates enabled.
