Skill Catalog
85 skills, baseline MariaDB 11.8 LTS. A skill is reference material the agent reads when it becomes relevant — it does not need a database, a connection or any configuration. Install a plugin and they are live.
How a skill gets used
You never invoke a skill. Each one carries a description saying
what it covers and when to use it, and the agent reads the ones that
match what you asked. Ask for a CREATE TABLE and it reads
mariadb-create-table; ask why a query is slow and it reads
mariadb-explain and mariadb-query-optimization.
That is why the output is MariaDB SQL rather than generic SQL. The skills
carry the version-specific detail a model would otherwise average away — that
MariaDB has a native UUID type, that utf8 means
utf8mb3, that there are no functional indexes, that
CREATE OR REPLACE is atomic.
The dev plugin ships all 85 of them. The smaller
sql variant carries 47 — the statement, function and topical layers
plus the create-script skill, but no connectors, REST or schema management.
SQL statements
31 skillsOne skill per statement, each covering the MariaDB-specific syntax and behaviour that a generic SQL answer gets wrong — online DDL algorithms on ALTER TABLE, atomic CREATE OR REPLACE, RETURNING on INSERT, IGNORED indexes, and so on.
- mariadb-create-table
- mariadb-alter-table
- mariadb-select
- mariadb-insert
- mariadb-update
- mariadb-delete
- mariadb-replace
- mariadb-create-view
- mariadb-create-index
- mariadb-drop-table
- mariadb-create-database
- mariadb-load-data
- mariadb-transactions
- mariadb-set-transaction
- mariadb-lock-tables
- mariadb-create-user
- mariadb-grant
- mariadb-revoke
- mariadb-alter-user
- mariadb-drop-user
- mariadb-create-procedure
- mariadb-create-function
- mariadb-create-trigger
- mariadb-call
- mariadb-create-sequence
- mariadb-truncate-table
- mariadb-rename-table
- mariadb-set
- mariadb-show
- mariadb-explain
- mariadb-prepare
Built-in functions
10 skillsThe function families, grouped by what they operate on. Includes the traps: aggregates skip NULLs, GROUP_CONCAT truncates silently at group_concat_max_len, and ONLY_FULL_GROUP_BY is not in the default sql_mode.
- mariadb-json-functions
- mariadb-string-functions
- mariadb-date-time-functions
- mariadb-numeric-functions
- mariadb-aggregate-functions
- mariadb-control-flow-functions
- mariadb-window-functions
- mariadb-information-functions
- mariadb-vector-functions
- mariadb-encryption-functions
Command-line tools
4 skillsThe client and utility programs — how batch mode changes the output format, what --flashback generates, and why mysql is still a symlink for the same binary.
- mariadb-dump
- mariadb-import
- mariadb-client
- mariadb-binlog
Connectors
14 skillsTwo skills per connector: installing and configuring it, and writing application code against it. Placeholder styles, autocommit defaults, prepared-statement behaviour and pooling all differ per connector, and are the usual source of bugs.
- mariadb-connector-python-install
- mariadb-connector-python-usage
- mariadb-connector-j-install
- mariadb-connector-j-usage
- mariadb-connector-nodejs-install
- mariadb-connector-nodejs-usage
- mariadb-connector-odbc-install
- mariadb-connector-odbc-usage
- mariadb-connector-r2dbc-install
- mariadb-connector-r2dbc-usage
- mariadb-connector-cpp-install
- mariadb-connector-cpp-usage
- mariadb-connector-c-install
- mariadb-connector-c-usage
Topical guides
5 skillsCross-cutting subjects that do not map to a single statement: query optimization, vector search, system-versioned tables, and what changes when an application moves from MySQL.
- mariadb-features
- mariadb-query-optimization
- mariadb-system-versioned-tables
- mysql-to-mariadb
- mariadb-vector
Shipped by this repository
21 skillsThe skills maintained here rather than vendored from the docs repo — the MariaDB REST Service DDL, the Schema Management lifecycle, the create-script conventions, and the MySQL-to-MariaDB migrator.
- mariadb-schema-create-script
- mariadb-rest-service-authorization
- mariadb-rest-service-create
- mariadb-rest-service-drop
- mariadb-rest-service-show
- mariadb-rest-service-update-endpoints
- mariadb-schema-management-create
- mariadb-schema-management-deploy
- mariadb-schema-management-develop
- mariadb-schema-management-release
- mariadb-schema-management
- mariadb-migrator-configure
- mariadb-migrator-discovery
- mariadb-migrator-modes
- mariadb-migrator-run
- mariadb-migrator-troubleshooting
- mariadb-migrator-verify
- mariadb-migrator
- mariadb-laravel-ai-sdk
- mariadb-laravel-connector
- mariadb-laravel-vector
Try them without a database
Every one of these works on a fresh install, with nothing configured. Some prompts that exercise a skill each:
Write a CREATE TABLE for a product catalogue, MariaDB style.
What changes if I move this application from MySQL to MariaDB?
How do I do semantic search in MariaDB?
Show me how to connect to MariaDB from Node.js, with a connection pool.
I need to track every change to this table for a compliance audit.
Explain what ALGORITHM=INSTANT can and cannot do on ALTER TABLE.
The fifth one is a good test of whether the skills are loaded: the answer should be system-versioned tables, a MariaDB feature with no MySQL equivalent, rather than a hand-rolled audit table with triggers.
Where they come from
Most skills are vendored from
mariadb-docs agent-skills/
and keep their original licenses. The
last group is maintained in this repository under
additional-skills/ and is GPL-2.0. The full list of sources and
their terms is in
additional-skills/README.md.
Vendoring is deliberate: the skills ship inside the plugin, so the version you have is the version you tested with, and a change upstream never surprises you mid-session.