agentsclimarketplace

Planetscale

Skill G1Joshi/Agent-Skills/skills/databases/planetscale

PlanetScale serverless MySQL with branching. Use for scalable MySQL.From its SKILL.md

Install
npx -y skills add G1Joshi/Agent-Skills --skill planetscale

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 390 tokens by cl100k_base, as published. Nobody here has run it

PlanetScale

PlanetScale is a serverless database platform compatible with MySQL. It is built on Vitess, the technology used by YouTube/Slack to scale massively.

When to Use

  • High Traffic MySQL: When you need "sharding" but don't want to build it yourself.
  • Schema Management: excellent "Branching" workflow (Development -> Staging -> Production) without downtime (Online DDL).
  • Connections: Handles 100,000s of concurrent connections (Vitess architecture).

Quick Start

Uses standard MySQL drivers.

# Connect via CLI
pscale shell my-database main

Core Concepts

Branching

Treat your database schema like Git code.

  1. Create a dev branch from main.
  2. Apply migrations to dev.
  3. Open a "Deploy Request" to merge dev to main.
  4. PlanetScale runs the schema change online without locking tables.

Vitess

Abstracts the sharding. Your app sees one big DB, but behind scenes it might be 100 shards.

Non-Blocking Schema Changes

Ghost/PT-OSC style schema changes standard. You never lock the table for "ALTER TABLE".

Best Practices (2025)

Do:

  • Use Foreign Keys carefully: PlanetScale supports them now (mostly), but conceptually in sharded systems, application-level joins are often safer/faster.
  • Use pscale CLI: Great developer experience for managing branches.
  • Safe Migrations: Use the Branching workflow. Never run ALTER TABLE directly on production main branch.

Don't:

  • Don't use stored procedures/triggers: Vitess generally discourages logic in the DB. Move logic to app.

References

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.