Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases. Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues.
90
81%
Does it follow best practices?
Impact
93%
1.16xAverage score across 8 eval scenarios
Passed
No known issues
VSchema design and sharding strategy
Shared primary vindex
50%
60%
Join co-location
70%
80%
xxhash vindex type
0%
100%
Vitess Sequences defined
60%
60%
Sequence in unsharded keyspace
90%
80%
auto_increment linked
100%
100%
Reference table for products
100%
100%
Reference table for tenants
100%
100%
Email lookup vindex
100%
100%
Lookup vindex owner set
100%
100%
No foreign keys in design
62%
100%
Query optimization for sharded tables
Scatter query identified
100%
100%
Vindex filter added
100%
100%
Correlated subquery rewritten
100%
100%
Cursor-based pagination
100%
100%
OLAP mode for analytics
100%
100%
Lookup vindex recommended
100%
100%
Avoid SELECT star
100%
100%
ORDER BY for determinism
100%
100%
Cross-shard join identified
100%
100%
VEXPLAIN mentioned
0%
100%
Aggregation memory warning
100%
100%
Schema migration planning
Vitess DDL strategy set
100%
100%
No direct DDL
100%
100%
Postpone-completion used
0%
100%
SHOW VITESS_MIGRATIONS
100%
100%
Tablet throttler mentioned
100%
100%
Revert command included
100%
100%
Cancel command included
100%
100%
Complete command for postponed
37%
100%
Migration UUID captured
100%
100%
Audit log co-located
100%
100%
Sequence for audit log
37%
37%
MySQL-to-Vitess migration compatibility
Stored procedure flagged
100%
100%
Trigger flagged
100%
100%
Event flagged
100%
100%
GET_LOCK flagged
100%
100%
LOCK TABLES flagged
100%
100%
SELECT FOR UPDATE warning
100%
100%
Foreign keys removed
100%
100%
AUTO_INCREMENT replaced
100%
100%
Booking logic rewritten
100%
100%
Clinic_id in booking query
100%
100%
Bulk update without LOCK
62%
100%
Reshard workflow and traffic switching
VDiff before switchtraffic
0%
100%
Reads switched first
100%
100%
Reverse traffic for rollback
100%
100%
Defer secondary keys
0%
100%
On-DDL stop flag
0%
100%
Correct shard ranges
100%
100%
Source shards specified
100%
100%
250GB shard target noted
0%
0%
Tablet throttler enabled
100%
0%
Complete command at end
0%
100%
Status monitoring included
100%
100%
Cross-shard transaction design
MULTI mode partial commit risk
75%
100%
2PC recommended for atomicity
100%
100%
Single-shard ACID noted
60%
50%
Co-location design proposed
30%
20%
Cross-shard transfer identified
100%
100%
Foreign key incompatibility flagged
100%
100%
AUTO_INCREMENT issue identified
20%
100%
SELECT FOR UPDATE warning
12%
0%
Transaction mode explanation
62%
100%
Schema-level fix proposed
100%
100%
Isolation level clarification
33%
100%
MoveTables vertical sharding workflow
MoveTables create command
100%
100%
Defer secondary keys flag
0%
100%
On-DDL stop flag
100%
100%
Sharded auto-increment handling
25%
100%
VDiff before switchtraffic
100%
100%
Reads switched before writes
100%
100%
Reversetraffic for rollback
100%
100%
Complete command at end
100%
100%
Status monitoring included
100%
100%
Tablet throttler enabled
100%
100%
Reverse replication preservation
100%
100%
Production Vitess architecture setup
Multiple VTGate instances
100%
100%
VTGate stateless noted
100%
100%
Replica tablets for OLTP reads
100%
100%
Rdonly tablets for analytics
100%
100%
VTOrc deployment
100%
100%
Etcd HA configuration
100%
100%
Replication lag monitoring
100%
100%
Single-etcd risk identified
100%
100%
Single-VTGate risk identified
100%
100%
OLAP mode for analytics
100%
100%
No-primary-only risk identified
100%
100%
b156f4c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.