What problem does it solve? Working with the MariaDB Kubernetes operator spans two distinct workflows—deploying the operator and clusters via Helm, and managing operator CRDs like Galera clusters, MaxScale, backups, and grants—and choosing the wrong approach wastes time and produces misconfigured resources. ## Core Features & Use Cases - Task Routing: Maps user requests to the correct sub-skill, either mariadb-operator for CRD management or mariadb-helm for Helm-based deployment. - CRD Operations Coverage: Directs Galera HA clusters, MaxScale read/write splitting, S3 backup schedules, Point-in-Time Recovery, SQL jobs, users, grants, and ExternalMariaDB resources to the operator sub-skill. - Helm Deployment Coverage: Directs operator installation, separate CRD installation, cluster provisioning, and cert-manager TLS setup to the Helm sub-skill. - Use Case: When asked to "set up MaxScale for read/write splitting," the router identifies this as a CRD task and loads mariadb-operator rather than the Helm deployment path. ## Quick Start Ask to create a MariaDB Galera cluster or deploy the MariaDB operator, and the router will load the appropriate sub-skill for the task.