Individual skill

mysql-replication-lag-resolver

Replication lag root cause analysis with automated resolution workflow. Detects lag, identifies blocking queries on the master, presents KILL candidates with safety classification, and executes KILL only after double user confirmation. Reduces recovery from 20 minutes to 2 minutes.

mysql-replication-lag-resolver/SKILL.md

Read pinned source

Source commit 6ac447941289a7aa25df36b1c8977704db7ba3f1

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 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)
174
Repository last updated
Jun 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# MySQL Replication Lag Resolver (Auto-Diagnose + Fix)

## Overview

Replication lag is one of the most critical database incidents — it means read replicas are falling behind the master, serving stale data to applications. Traditional resolution requires DBA to: receive alert → open laptop → connect VPN → login to jumpbox → check slave status → find blocking queries on master → decide what to kill → execute KILL → monitor recovery. **20+ minutes at 2 AM.**

This skill automates the entire diagnosis and presents a one-click resolution:

1. **Detect** — Check Seconds_Behind_Master and replication health
2. **Root Cause** — Find long-running queries on master blocking binlog sync
3. **Classify** — Mark each query as safe/caution/dangerous to kill
4. **Present** — Show candidates with impact analysis
5. **Resolve** — Execute KILL with double user confirmation
6. **Verify** — Monitor lag recovery in real-time