More screenshots
Works with the AI Agents you already use
Repair MySQL GTID Errant Transaction Replica Block
Diagnose stopped MySQL replication after divergent GTID execution without unsafe skips
$1
Repair MySQL GTID Errant Transaction Replica Block
Example session with this skill installed
A replica has a locally executed GTID that does not exist on primary and cannot rejoin cleanly.
Available sources: GTID executed sets and binary log positions (partial excerpts only). Additional evidence requested: replication errors, role history. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair mysql gtid
Repair MySQL GTID Errant Transaction Replica Block — EVIDENCE-LIMITED REVIEW
Scenario received
A replica has a locally executed GTID that does not exist on primary and cannot rejoin cleanly.
Source register
- S1: GTID executed sets — partial extract described, independent verification not provided.
- S2: binary log positions — partial extract described, independent verification not provided.
- S3: replication errors — NOT PROVIDED; validation pending.
- S4: role history — NOT PROVIDED; validation pending.
Case-specific checks
- compare primary and replica GTID sets — NEEDS VERIFICATION against S1/S2 and missing sources.
- identify origin of errant transaction — NEEDS VERIFICATION against S1/S2 and missing sources.
- assess logical data divergence — NEEDS VERIFICATION against S1/S2 and missing sources.
propose backup-led reconstruction or controlled remediation — NEEDS VERIFICATION against S1/S2 and missing sources.
Deliverables and review gates
- GTID delta map: DRAFT ONLY; do not infer unsupported outcomes.
- data divergence risk: DRAFT ONLY; do not infer unsupported outcomes.
- operator recovery gates: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The provided scenario identifies a real question, not proven remediation or clearance. Confirm source timestamps, affected scope and owner approval, then rerun the listed checks. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair MySQL GTID Errant Transaction Replica Block is a ToolForge Labs ChatGPT Skill workflow. Diagnose stopped MySQL replication after divergent GTID execution without unsafe skips.
What this skill checks
- compare primary and replica GTID sets.
- identify origin of errant transaction.
- assess logical data divergence.
- propose backup-led reconstruction or controlled remediation.
What to provide
- GTID executed sets.
- binary log positions.
- replication errors.
- role history.
Deliverables
- GTID delta map.
- data divergence risk.
- operator recovery gates.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 25 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.