mysql

MySQL relational database with InnoDB, replication, and stored procedures. Use for MySQL operations.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

mysql is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

MySQL relational database with InnoDB, replication, and stored procedures. Use for MySQL operations.

Teams using mysql should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/mysql/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/databases/mysql/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/mysql/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How mysql Compares

Feature / Agent	mysql	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

MySQL relational database with InnoDB, replication, and stored procedures. Use for MySQL operations.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# MySQL

MySQL is a widely used relational database management system (RDBMS). It is the "M" in the LAMP stack and powers huge platforms like Facebook and WordPress.

## When to Use

- **Web Applications**: Standard for PHP/Laravel/Wordpress ecosystems.
- **Read-Heavy Workloads**: Historically very fast for simple read operations.
- **Replication**: Huge ecosystem of tools for Master-Slave replication and clustering (Galera, InnoDB Cluster).

## Quick Start

```sql
-- Upsert (Insert or Update)
INSERT INTO users (id, name) VALUES (1, 'Jane')
ON DUPLICATE KEY UPDATE name = 'Jane';
```

## Core Concepts

### Storage Engines

- **InnoDB**: The default. Supports transactions (ACID), row-level locking, and foreign keys. **Always use this**.
- **MyISAM**: Legacy. Fast reads but table-level locking and no transactions. Avoid.

### Explain

Prefix any query with `EXPLAIN` to see how MySQL executes it (indexes used, rows scanned).

```sql
EXPLAIN SELECT * FROM users WHERE email = 'test@test.com';
```

### Replication

MySQL replication is often asynchronous by default, meaning slaves might lag behind master.

## Best Practices (2025)

**Do**:

- **Use MySQL 8.4+**: For LTS features like `EXPLAIN ANALYZE` and CTE support.
- **Use `utf8mb4`**: The _real_ UTF-8. The standard `utf8` in MySQL is a partial implementation (max 3 bytes).
- **Disable `mysql_native_password`**: In 8.4+, use `caching_sha2_password` for security.

**Don't**:

- **Don't use MyISAM**: It is effectively obsolete for modern apps.
- **Don't store logic in Stored Procedures**: Hard to version control and debug. Keep logic in the app layer.

## References

- [MySQL 8.4 Reference Manual](https://dev.mysql.com/doc/refman/8.4/en/)