Migrate configuration files between formats and versions with environment variable extraction
Scanned 9/2/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill configuration-migrator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Configuration Migrator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-configuration-migrator-babysitter)More formats (shields.io, HTML) on the badges page.
---
name: configuration-migrator
description: Migrate configuration files between formats and versions with environment variable extraction
allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob", "Edit"]
graph:
domains: [domain:software-engineering]
specializations: [specialization:code-migration-modernization]
skillAreas: [skill-area:configuration-management, skill-area:dependency-upgrade-strategies]
roles: [role:devops-engineer, role:backend-engineer]
workflows: [workflow:technical-debt-reduction]
topics: [topic:refactoring]
---
# Configuration Migrator Skill
Migrates configuration files between different formats and versions, handles environment variable extraction, and manages secret detection.
## Purpose
Enable configuration migration for:
- Config format conversion
- Environment variable extraction
- Secret detection and handling
- Schema validation
- Template generation
## Capabilities
### 1. Config Format Conversion
- XML to YAML/JSON
- Properties to YAML
- INI to JSON
- TOML conversion
- ENV file handling
### 2. Environment Variable Extraction
- Identify environment-specific values
- Extract to env files
- Create variable references
- Document variables
### 3. Secret Detection
- Find hardcoded secrets
- Identify credentials
- Detect API keys
- Flag sensitive data
### 4. Schema Validation
- Validate against schemas
- Check required fields
- Verify data types
- Ensure compatibility
### 5. Default Value Handling
- Preserve defaults
- Document required overrides
- Create sensible defaults
- Handle missing values
### 6. Template Generation
- Create config templates
- Generate example files
- Document all options
- Support multiple environments
## Tool Integrations
| Tool | Purpose | Integration Method |
|------|---------|-------------------|
| yq | YAML processing | CLI |
| jq | JSON processing | CLI |
| dotenv | ENV file handling | Library |
| git-secrets | Secret detection | CLI |
| Config validators | Schema validation | CLI |
## Output Schema
```json
{
"migrationId": "string",
"timestamp": "ISO8601",
"source": {
"format": "string",
"path": "string"
},
"target": {
"format": "string",
"path": "string"
},
"conversions": [
{
"sourceKey": "string",
"targetKey": "string",
"transformation": "string"
}
],
"extracted": {
"envVariables": [],
"secrets": []
},
"validation": {
"valid": "boolean",
"errors": [],
"warnings": []
}
}
```
## Integration with Migration Processes
- **configuration-migration**: Primary tool
- **framework-upgrade**: Config version updates
- **cloud-migration**: Cloud config adaptation
## Related Skills
- `compliance-validator`: Secret compliance
## Related Agents
- `configuration-centralization-agent`: Config modernization

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!