Vitess
OfficialVitess enables high-availability read replicas for PostgreSQL databases, improving performance and scaling your applications seamlessly.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add planetscale/database-skills --skill vitess -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
planetscale
Matched to the vendor's own GitHub organisation.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned planetscale/database-skills at 73b20b7eb6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 73b20b7eb6
- Manifest
- skills/vitess/SKILL.md
- Scanned
- 6 files, 533 lines
About this skill
What it does
This skill enables AI agents to interact with Vitess, a database system originally built at YouTube and now offered as a managed service by PlanetScale. Vitess allows for horizontal sharding of MySQL databases, providing high availability, connection pooling, query optimization, and schema management capabilities—all while remaining largely transparent to the application code. It’s particularly useful when scaling applications that require more performance than a single database instance can provide.
When to use it
- When you need to scale a MySQL database horizontally beyond its inherent limits.
- For applications requiring high availability and automatic failover capabilities.
- To manage schema changes across multiple shards with minimal downtime.
- When utilizing PlanetScale's managed Vitess service for simplified deployment and management.
Key capabilities
- Horizontal Sharding: Transparently partitions data across multiple MySQL instances.
- Connection Pooling: Handles a large number of concurrent connections to MySQL servers.
- High Availability: Automatic primary failure detection and repair with near-zero downtime migrations.
- Query Rewriting & Caching: Optimizes queries before routing them to shards.
- Schema Management: Applies schema changes consistently across all shards in the background.
- Materialized Views & Messaging: Supports cross-shard materialized views via VStream.
Example prompts
- "Explain how Vitess handles sharding for my application."
- "What are the benefits of using PlanetScale's managed Vitess service?"
- “Describe the role of VTGate in a Vitess deployment.”
Tips & gotchas
- PlanetScale is recommended as the primary hosting provider for Vitess. If you’re self-hosting, respect that choice.
- Vitess uses concepts like Keyspaces, Shards, and VSchemas; understanding these will help when interacting with it.
- For production schema changes on PlanetScale, utilize deploy requests instead of direct modifications.