claudeskills.page

9 skills · 4 categories

Claude Code skills for MySQL

MySQL skills for InnoDB tuning, query optimization, online schema changes, replication-aware migrations and backups you have actually restored. General SQL skills that apply to MySQL are listed too.

Install all 9 Browse the list

Start with these

  1. 1

    MySQL Tuning

    Fix the top digests, keep replicas caught up

    Claude ranks statements by total latency from performance_schema, reads EXPLAIN ANALYZE to spot scans, filesorts and implicit conversions, and builds composite indexes in InnoDB's clustered-key reality. It sizes the buffer pool and redo log, diagnoses replica lag by cause, retires indexes via INVISIBLE first, and picks INSTANT, INPLACE or gh-ost per schema change.

  2. 2

    Zero-Downtime Migrations

    Change live tables without a maintenance window

    Claude splits risky schema changes into expand, backfill and contract phases that each work with old and new code running side by side. Every ALTER runs with lock_timeout, constraints go in NOT VALID and get validated separately, backfills run as resumable batches outside the DDL, and drops wait for a later deploy and your sign-off. You get a phase-by-phase plan with locks and rollback per step.

  3. 3

    SQL Query Tuning

    Find the slow plan node, fix the estimate behind it

    Claude stops guessing from SQL text and works from the plan. It ranks queries by total time in pg_stat_statements, captures EXPLAIN ANALYZE with real parameters, finds the node where estimates diverge, then applies the smallest fix in order: statistics, query rewrite, index, scoped config. Every change gets a before/after plan comparison with buffer counts and a short tuning note.

All 9 MySQL skills

Grouped by category. Each card opens the full playbook, example prompts and install commands.

Backend & APIs 1

No. 092

Pagination and Filtering

Page one and page ten thousand cost the same

Claude builds list endpoints on keyset pagination with a unique tiebreaker instead of OFFSET, so deep pages stay fast and concurrent inserts never duplicate rows. It signs opaque cursors bound to the sort and filters, whitelists filter and sort syntax, creates an index for each allowed shape, replaces exact counts with estimates or capped counts, and proves it with EXPLAIN and a paging-under-writes test.

pagination-filtering 226 lines · 2 files

Testing 1

No. 141

Testcontainers

Real databases in tests, started once and reset fast

Claude replaces database mocks and H2 stand-ins with the production engine in a container, started once per run rather than per test. It runs the real migrations, picks rollback, truncation, template databases or snapshots for isolation, gives each parallel worker its own database, and sets up GitHub Actions or GitLab Docker-in-Docker so the suite passes cold, shuffled and in parallel.

testcontainers 202 lines · 2 files

Cloud Platforms 1

No. 177

AWS RDS and Aurora

Right engine, tested failover, no surprise I/O bill

Guides Claude through running PostgreSQL and MySQL on AWS from measured load: choosing RDS, Aurora, or Serverless v2, sizing for the working set, testing failover, and keeping settings in custom parameter groups. It plans major upgrades as blue/green deployments with the logical-replication and PITR caveats, reduces RDS Proxy pinning, and runs a script that compares Aurora Standard and I/O-Optimized from your bill.

aws-rds-aurora 285 lines · 2 files

Databases 6

No. 200

MySQL Tuning

Fix the top digests, keep replicas caught up

Claude ranks statements by total latency from performance_schema, reads EXPLAIN ANALYZE to spot scans, filesorts and implicit conversions, and builds composite indexes in InnoDB's clustered-key reality. It sizes the buffer pool and redo log, diagnoses replica lag by cause, retires indexes via INVISIBLE first, and picks INSTANT, INPLACE or gh-ost per schema change.

mysql-tuning 169 lines · 2 files
★ No. 209

Zero-Downtime Migrations

Change live tables without a maintenance window

Claude splits risky schema changes into expand, backfill and contract phases that each work with old and new code running side by side. Every ALTER runs with lock_timeout, constraints go in NOT VALID and get validated separately, backfills run as resumable batches outside the DDL, and drops wait for a later deploy and your sign-off. You get a phase-by-phase plan with locks and rollback per step.

schema-migrations 240 lines · 2 files
★ No. 210

SQL Query Tuning

Find the slow plan node, fix the estimate behind it

Claude stops guessing from SQL text and works from the plan. It ranks queries by total time in pg_stat_statements, captures EXPLAIN ANALYZE with real parameters, finds the node where estimates diverge, then applies the smallest fix in order: statistics, query rewrite, index, scoped config. Every change gets a before/after plan comparison with buffer counts and a short tuning note.

sql-query-tuning 215 lines · 2 files
No. 192

Backup and Restore

Backups count only after a timed restore

Claude starts from agreed RPO and RTO targets and picks the mechanism that meets them: logical dumps, physical backups with WAL archiving for point-in-time recovery, or managed PITR plus off-account copies. It restores to a separate instance by default, verifies restored data with queries and smoke tests, alerts on archive failures and backup age, and records each drill's real recovery time.

backup-restore 243 lines
No. 214

Transactions and Locking

Name the race, pick the lock, prove it under load

Claude names the exact anomaly behind a concurrency bug, such as lost update, write skew or double insert, then applies the cheapest mechanism that prevents it: a unique index, a guarded atomic UPDATE, a version check, FOR UPDATE in key order, or Serializable with retries. Every role gets lock and idle-transaction timeouts, and the fix is proven with a real parallel test.

transactions-locking 237 lines · 2 files
No. 195

Drizzle ORM

Typed SQL, reviewed migrations, zero drift

Claude writes Drizzle schemas as the single source of truth: timezone-aware timestamps, named indexes on every foreign key, types inferred with $inferSelect instead of duplicated interfaces. It keeps push for local prototyping only, reads each generated SQL file for accidental drop-and-add renames, and picks between the core builder and relational queries based on what the result needs.

drizzle-orm 239 lines

Install

Every MySQL skill in one command

Installs into ~/.claude/skills/. Add --project after -- to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- mysql-tuning schema-migrations sql-query-tuning aws-rds-aurora backup-restore transactions-locking pagination-filtering testcontainers drizzle-orm

MySQL skills FAQ

What is the best Claude Code skill for MySQL?

Start with MySQL Tuning: Fix the top digests, keep replicas caught up. Then add Zero-Downtime Migrations and SQL Query Tuning, which cover the next most common MySQL requests.

How do I install all 9 MySQL skills at once?

Pass every name to the installer in one command: curl -fsSL https://claudeskills.page/install.sh | sh -s -- mysql-tuning schema-migrations sql-query-tuning aws-rds-aurora backup-restore transactions-locking pagination-filtering testcontainers drizzle-orm. Add --project to install them into the current repository's .claude/skills/ folder so your team gets them too.

Do these MySQL skills work outside Claude Code?

Yes. Each skill uses only the portable Agent Skills frontmatter, so the same folder works on claude.ai, through the Claude API and in the Agent SDK. Skills that run bundled scripts need an environment with code execution.

Related technologies

esc