Individual skill
mysql
Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.
.agent/skills/mysql/SKILL.md
Source commit eba65ebbb0a78c4a7fd25aab28e94966eddbca5b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 336
- Repository last updated
- Aug 31, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- ai Repository topic
- claude-code Repository topic
- codex Repository topic
- prd Repository topic
- ralph Repository topic
- ralph-loop Repository topic
- ralph-wiggum Repository topic
- operations Derived category
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,241 bytesreferences/character-sets.mddoc · 2,382 bytesreferences/composite-indexes.mddoc · 2,719 bytesreferences/connection-management.mddoc · 4,096 bytesreferences/covering-indexes.mddoc · 2,000 bytesreferences/data-types.mddoc · 2,389 bytesreferences/deadlocks.mddoc · 3,355 bytesreferences/explain-analysis.mddoc · 2,887 bytesreferences/fulltext-indexes.mddoc · 1,649 bytesreferences/index-maintenance.mddoc · 3,809 bytesreferences/isolation-levels.mddoc · 3,242 bytesreferences/json-column-patterns.mddoc · 3,192 bytesreferences/n-plus-one.mddoc · 2,935 bytesreferences/online-ddl.mddoc · 2,584 bytesreferences/partitioning.mddoc · 3,605 bytesreferences/primary-keys.mddoc · 3,573 bytesreferences/query-optimization-pitfalls.mddoc · 3,841 bytesreferences/replication-lag.mddoc · 2,909 bytesreferences/row-locking-gotchas.mddoc · 3,198 bytes
Read excerpt
# MySQL
Use this skill to make safe, measurable MySQL/InnoDB changes.
## Workflow
1. Define workload and constraints (read/write mix, latency target, data volume, MySQL version, hosting platform).
2. Read only the relevant reference files linked in each section below.
3. Propose the smallest change that can solve the problem, including trade-offs.
4. Validate with evidence (`EXPLAIN`, `EXPLAIN ANALYZE`, lock/connection metrics, and production-safe rollout steps).
5. For production changes, include rollback and post-deploy verification.
## Schema Design
- Prefer narrow, monotonic PKs (`BIGINT UNSIGNED AUTO_INCREMENT`) for write-heavy OLTP tables.
- Avoid random UUID values as clustered PKs; if external IDs are required, keep UUID in a secondary unique column.