ericrisco/rsc-harness / skills/planetscale
planetscale
VerifiedUse when operating PlanetScale (Vitess serverless MySQL) — branches and the `pscale` CLI, schema changes through deploy requests (Online DDL cutover, ~30-min revert window), tables without foreign keys, or the edge HTTP driver. NOT MySQL engine work like EXPLAIN or index choice (that is `mysql`), NOT generic migration theory (that is `db-migrations`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.0 KB |
| evals/README.md | markdown | 912 B |
| evals/cases.yaml | config | 4.0 KB |
| references/deploy-requests.md | markdown | 3.9 KB |
| references/no-foreign-keys.md | markdown | 3.8 KB |
| scripts/verify.shexecutable | script | 4.8 KB |
evals/README.md
View on GitHub# Evals — planetscale
`cases.yaml` holds prompt-routing checks and capability rubrics for the repo's eval harness. The
`should_trigger` / `should_not_trigger` entries assert routing: an LLM grader decides whether each
prompt would invoke the planetscale skill, and the `should_not_trigger` cases name the real sibling it
should go to instead (mysql, postgresdb, neon, db-migrations, prisma-orm). The `capability` entry is a
scenario graded against its `must_include` rubric — the model's answer must hit each bullet (dev
branch, branch-scoped DDL, `pscale deploy-request create`/`diff`, Online DDL shadow-copy/cutover,
auto-apply vs manual apply, the ~30-minute revert window and its carve-outs, and a no-FK table design).
No live PlanetScale account, `pscale` CLI, or database is needed — everything is graded from the model's
text. Run it through the repo's standard eval runner against this directory.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |