ericrisco/rsc-harness / skills/mysql
mysql
VerifiedUse when designing, querying, indexing or operating a MySQL or MariaDB database and engine-specific behaviour matters — schema and type choices, index design, reading EXPLAIN, online schema change, replication and replica lag, locking and InnoDB deadlocks, charset traps, and server config. NOT portable SELECT/JOIN/window-function craft (that is `sql`), NOT PostgreSQL engine behaviour like VACUUM or JSONB (that is `postgresdb`), NOT the PlanetScale/Vitess branch-and-deploy workflow (that is `planetscale`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.7 KB |
| evals/README.md | markdown | 983 B |
| evals/cases.yaml | config | 3.5 KB |
| references/indexing-and-explain.md | markdown | 7.3 KB |
| references/mysql-vs-mariadb.md | markdown | 4.6 KB |
| references/online-ddl-and-migrations.md | markdown | 5.9 KB |
| references/replication-and-ha.md | markdown | 5.5 KB |
| scripts/verify.shexecutable | script | 6.6 KB |
evals/README.md
View on GitHub# Evals — mysql
These cases are routing and capability specs, not an automated test suite. There is no in-repo
trigger harness. To run them, have a human or an LLM judge read `cases.yaml` and check three things:
that each `should_trigger` prompt would plausibly load this skill, that each `should_not_trigger`
prompt routes to the named sibling instead (`sql`, `postgresdb`, `planetscale`, `db-migrations`,
`drizzle-orm` — all real skills), and that an answer to the `capability` scenario hits every bullet
in its `must_include` rubric. The rubric is the bar: a passing answer reads EXPLAIN, fixes the
non-sargable predicate, designs the composite/covering index with correct column order, reasons
about the InnoDB clustered index, and verifies the new plan — without drifting into ORM or platform
workflow that belongs to a sibling. `scripts/verify.sh` is separate: it lints emitted `*.sql` /
`*.cnf` artifacts for the foot-guns in SKILL.md and never connects to a database.
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 |