What problem does it solve? Installing the mariadb Python module fails or misbehaves when the wrong install variant is chosen: the 1.1 GA line always builds the C extension and needs MariaDB Connector/C 3.3.1+ with mariadb_config on the PATH, while the pure-Python, binary-wheel, and pooling variants exist only on the 2.0 line and require pip install --pre. This Skill prevents build failures, container runtime errors, and insecure TLS defaults. ## Core Features & Use Cases - Correct install variant selection: Distinguishes 1.1 GA (pip install mariadb) from 2.0 RC variants (mariadb[c], mariadb[binary], mariadb[pool]), including Python floor requirements (3.8 vs 3.10) and Windows guidance. - Build failure diagnosis: Explains that mariadb_config not found means the Connector/C development package (libmariadb-dev or MariaDB-devel) is missing, not the compiler, and how to point at it via site.cfg. - Configuration guidance: Covers option files (default_file, default_group), TLS settings including the 1.1 ssl_verify_cert=False default, and ConnectionPool sizing. - Use Case: When building a slim Docker image where import mariadb fails at runtime, this Skill directs you to install libmariadb3 in the final stage or use the 2.0 mariadb[binary] wheel that bundles Connector/C. ## Quick Start Ask the AI to install and configure the MariaDB Connector/Python module for your environment, for example by requesting the correct pip command and Connector/C prerequisites for a Debian container targeting the stable release.