Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides specialized knowledge for managing MySQL and PostgreSQL environments. It assists database administrators and developers in refining indexing strategies, tuning queries, and diagnosing locking behavior to ensure stable performance.
The skills focus on the practicalities of database maintenance, from planning migrations and schema changes to troubleshooting replication and connection issues.
WHO IT'S FOR
Database Administrators
diagnosing slow or locking database behavior
Backend / infrastructure engineers
planning database migrations and schema changes
AI agent / automation builders
integrating database optimization into AI workflows
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
One slow SQL query, relevant table definitions, existing indexes, and EXPLAIN output.
MySQL version, hosting platform, read/write mix, approximate data volume, and latency target.
Use the mysql skill to review the slow query, table definitions, indexes, and EXPLAIN output I provide. Identify the main performance concern and propose the smallest query or index change, explaining trade-offs and how to validate it. Consider my MySQL version, hosting platform, workload, data volume, and latency target.
Relevant VSchema, vindex columns, and keyspace sharding configuration.
Use the vitess skill to review one query against my sharded tables and VSchema. Explain whether its predicates support single-shard routing, flag cross-shard joins or aggregation costs, and suggest one small improvement based on the supplied query and routing configuration.
One transaction's SQL, including session settings and their order relative to BEGIN.
Relevant data topology, shard keys, and shard group or shard index configuration.
Use the neki skill to review the transaction SQL, session settings, and data topology I provide. Check whether the transaction stays on one shard, identify assumptions about cross-shard atomicity or shared snapshots, and flag incorrect __neki.* setting names or settings applied after BEGIN. Recommend the smallest correction without executing changes.
Cursor