Manages schema evolution and compatibility across data systems
Scanned 9/2/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill schema-evolution-manager --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Schema Evolution Manager?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-schema-evolution-manager-babysitter)More formats (shields.io, HTML) on the badges page.
---
name: Schema Evolution Manager
description: Manages schema evolution and compatibility across data systems
version: 1.0.0
category: Data Governance
skillId: SK-DEA-011
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
- Bash
graph:
domains: [domain:data-engineering]
specializations: [specialization:data-engineering-analytics]
skillAreas: [skill-area:schema-evolution, skill-area:data-governance]
roles: [role:data-engineer, role:analytics-engineer]
workflows: [workflow:data-pipeline-deployment]
topics: [topic:data-mesh]
---
# Schema Evolution Manager
## Overview
Manages schema evolution and compatibility across data systems. This skill ensures safe schema changes that maintain backward and forward compatibility.
## Capabilities
- Schema compatibility checking (Avro, Protobuf, JSON Schema)
- Breaking change detection
- Migration script generation
- Version management
- Schema registry operations
- Backward/forward compatibility validation
- Schema documentation generation
- Cross-system schema synchronization
## Input Schema
```json
{
"currentSchema": "object",
"proposedSchema": "object",
"schemaFormat": "avro|protobuf|jsonschema|ddl",
"compatibilityMode": "backward|forward|full|none"
}
```
## Output Schema
```json
{
"compatible": "boolean",
"breakingChanges": ["object"],
"migrationScript": "string",
"recommendations": ["string"],
"versionInfo": "object"
}
```
## Target Processes
- Streaming Pipeline
- ETL/ELT Pipeline
- Data Catalog
- Pipeline Migration
## Usage Guidelines
1. Provide current and proposed schema definitions
2. Specify schema format for proper parsing
3. Define compatibility mode based on system requirements
4. Review breaking changes before proceeding with migration
## Best Practices
- Always test schema changes in non-production first
- Use schema registry for centralized schema management
- Document schema versions and changes
- Plan migration strategies for breaking changes
- Coordinate schema changes across dependent systems
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!