More screenshots
Works with the AI Agents you already use
Repair Debezium MySQL DDL History Topic Recovery
Rebuild a trustworthy CDC schema-history continuity check after a Debezium connector restart
$1
Repair Debezium MySQL DDL History Topic Recovery
Example session with this skill installed
A connector restarts with an empty history topic and silently rejects two ALTER TABLE revisions.
Available sources: connector config, schema history offsets (partial excerpts only). Additional evidence requested: DDL log, CDC error trace. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair debezium mysql
Repair Debezium MySQL DDL History Topic Recovery — EVIDENCE-LIMITED REVIEW
Scenario received
A connector restarts with an empty history topic and silently rejects two ALTER TABLE revisions.
Source register
- S1: connector config — partial extract available.
- S2: schema history offsets — partial extract available.
- S3: DDL log — NOT PROVIDED; REQUIRED FOR VERIFICATION.
- S4: CDC error trace — NOT PROVIDED; REQUIRED FOR VERIFICATION.
Concrete findings and verification
compare history topic retention to connector offset — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
2.
replay ordered DDL revisions in isolation — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
3. identify earliest schema mismatch — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
4.
propose reversible recovery and validation — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
Deliverables and review gates
- history coverage ledger: DRAFT ONLY; do not infer unsupported outcomes.
- affected table and offset map: DRAFT ONLY; do not infer unsupported outcomes.
- safe recovery test plan: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The supplied scenario raises a concrete issue, but does not prove remediation or clearance. Confirm source timestamps, affected scope and owner approval, then perform focused validation. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Broken Change Data Capture (CDC) pipelines often fail silently when a Debezium connector restarts with an empty history topic. This skill provides a technical framework for rebuilding a trustworthy schema-history continuity check. It eliminates the guesswork involved in identifying why a connector is rejecting ALTER TABLE revisions or failing to sync schema changes after a crash.
What it does
- Analyze history retention: Compares history topic retention settings against connector offsets to find gaps.
- Replay DDL revisions: Replays ordered DDL changes in isolation to verify schema state.
- Pinpoint mismatches: Identifies the exact offset and identifier where the schema mismatch first occurred.
- Generate recovery plans: Proposes reversible recovery steps and validation gates for operators.
How it works
- Input collection: Provide the connector configuration, schema history offsets, DDL logs, and the CDC error trace.
- Evidence analysis: The skill runs four specific checks across retention, DDL ordering, and mismatch identification.
- Verdict delivery: You receive a technical verdict (SUPPORTED, BLOCKED, or UNVERIFIED) based on the evidence.
- Execution planning: The skill generates a history coverage ledger and a safe recovery test plan.
Frameworks & tools
This skill is designed for Debezium MySQL connectors, Kafka Connect, and schema history topics.
Why this beats prompting it yourself
Generic prompts often suggest destructive "reset and restart" approaches that lose data. This skill enforces an evidence-first workflow with hard gates, ensuring that every recommendation is reversible and linked to specific log identifiers.
Use cases
- Recover a Debezium connector after a silent DDL history topic purge.
- Debug "schema not found" errors during Kafka Connect restarts.
- Validate DDL log integrity before resuming a production CDC pipeline.
- Audit history coverage gaps between source MySQL and Kafka topics.
Known limitations
This skill evaluates provided evidence and does not execute commands directly. It requires manual redaction of sensitive data from logs.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.
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 24 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.