CDC Pattern Implementer
DevelopmentCDC Pattern Implementer is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Implements Change Data Capture patterns for real-time data integration
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/data-engineering-analytics/skills/cdc-pattern-implementer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cdc-pattern-implementer, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
CDC Pattern Implementer
Overview
Implements Change Data Capture patterns for real-time data integration. This skill provides expertise in CDC configuration and implementation across various database and streaming platforms.
Capabilities
- Debezium connector configuration
- CDC pattern selection (log-based, trigger-based, timestamp-based)
- Initial snapshot strategy
- Schema change handling
- Exactly-once delivery configuration
- Sink connector setup
- Tombstone handling
- CDC monitoring setup
Input Schema
{
"sourceDatabase": {
"type": "postgres|mysql|oracle|sqlserver",
"connection": "object"
},
"tables": ["string"],
"targetSystem": "kafka|kinesis|pubsub",
"requirements": {
"latencyMs": "number",
"exactlyOnce": "boolean"
}
}
Output Schema
{
"connectorConfig": "object",
"snapshotStrategy": "object",
"schemaConfig": "object",
"monitoringConfig": "object",
"documentation": "string"
}
Target Processes
- ETL/ELT Pipeline
- Streaming Pipeline
- Data Warehouse Setup
Usage Guidelines
- Identify source database and tables for CDC
- Define target streaming system
- Specify latency and delivery guarantees
- Configure appropriate snapshot strategy for initial load
Best Practices
- Use log-based CDC when possible for minimal source impact
- Plan initial snapshot strategy carefully for large tables
- Implement proper error handling and dead letter queues
- Monitor replication lag and connector health
- Test schema evolution handling before production