How do I install the Mysql Principal Engineer skill?

Run npx skillmds@latest add modra40/mysql-principal-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mysql Principal Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mysql Principal Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mysql Principal Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mysql Principal Engineer?

modra40 (@modra40) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mysql Principal Engineer by modra40

Name: Mysql Principal Engineer
Author: modra40

Mysql Principal Engineer

Principal/Senior-level MySQL playbook for schema design, indexing, transactions, replication, operational reliability, online migrations, and production workload tuning. Use when: designing relational systems, reviewing query/index strategy, operating MySQL fleets, debugging contention or replication lag, or hardening MySQL-backed applications.

modra40 baa413f 9 files · 8.9 KB Updated Sep 17, 2026

File contents

MySQL Mastery (Senior → Principal)

Operate

Start from workload shape, consistency requirements, and operational model.
Treat MySQL as a production system: schema, indexes, replication, backups, failover, and migrations all matter.
Prefer explicit transactional boundaries and predictable query patterns.
Optimize for boring operations rather than magical ORM assumptions.

Default Standards

Model invariants with schema and transactions first.
Index for real query patterns and sort paths.
Keep long transactions and lock-heavy flows visible.
Replication lag and failover behavior must be known, not guessed.
Online change workflows need review before rollout.

References

Schema design and indexing: references/schema-design-and-indexing.md
Query planning and performance: references/query-planning-and-performance.md
Transactions, locks, and isolation: references/transactions-locks-and-isolation.md
Replication, lag, and failover: references/replication-lag-and-failover.md
Online migrations and operational change: references/online-migrations-and-operational-change.md
Backup, restore, and disaster recovery: references/backup-restore-and-disaster-recovery.md
Reliability and operations: references/reliability-and-operations.md
Incident runbooks: references/incident-runbooks.md

---name: mysql-principal-engineerdescription: Principal/Senior-level MySQL playbook for schema design, indexing, transactions, replication, operational reliability, online migrations, and production workload tuning. Use when: designing relational systems, reviewing query/index strategy, operating MySQL fleets, debugging contention or replication lag, or hardening MySQL-backed applications.---# MySQL Mastery (Senior → Principal)## Operate- Start from workload shape, consistency requirements, and operational model.- Treat MySQL as a production system: schema, indexes, replication, backups, failover, and migrations all matter.- Prefer explicit transactional boundaries and predictable query patterns.- Optimize for boring operations rather than magical ORM assumptions.## Default Standards- Model invariants with schema and transactions first.- Index for real query patterns and sort paths.- Keep long transactions and lock-heavy flows visible.- Replication lag and failover behavior must be known, not guessed.- Online change workflows need review before rollout.## References- Schema design and indexing: [references/schema-design-and-indexing.md](references/schema-design-and-indexing.md)- Query planning and performance: [references/query-planning-and-performance.md](references/query-planning-and-performance.md)- Transactions, locks, and isolation: [references/transactions-locks-and-isolation.md](references/transactions-locks-and-isolation.md)- Replication, lag, and failover: [references/replication-lag-and-failover.md](references/replication-lag-and-failover.md)- Online migrations and operational change: [references/online-migrations-and-operational-change.md](references/online-migrations-and-operational-change.md)- Backup, restore, and disaster recovery: [references/backup-restore-and-disaster-recovery.md](references/backup-restore-and-disaster-recovery.md)- Reliability and operations: [references/reliability-and-operations.md](references/reliability-and-operations.md)- Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)

Frequently asked questions