What problem does it solve? Writing vector similarity search SQL in MariaDB is error-prone because the feature is new (11.7 preview, 11.8 LTS GA), has no pgvector-style distance operators, and imposes strict index-matching rules. This Skill provides the correct function signatures, version constraints, and common pitfalls so generated SQL works the first time. ## Core Features & Use Cases - Function Catalog: Reference for VEC_DISTANCE, VEC_DISTANCE_EUCLIDEAN, VEC_DISTANCE_COSINE, VEC_FromText, and VEC_ToText with signatures and semantics. - Pitfall Corrections: Maps common wrong assumptions (pgvector <-> operators, automatic JSON array conversion, normalized similarity scores) to the correct MariaDB forms. - Index Usage Rules: Explains when ORDER BY ... LIMIT actually uses the VECTOR INDEX, the one-index-per-table limit, and metric matching requirements. - Use Case: When asked to write a k-nearest-neighbor query over stored embeddings, produce ORDER BY VEC_DISTANCE_EUCLIDEAN(embedding, VEC_FromText('[...]')) LIMIT 10 with the correct index and version checks. ## Quick Start Write a MariaDB 11.8 query that finds the 10 nearest embeddings to a given vector using cosine distance and tell me whether it will use the vector index.