configuration-migrator
Migrate configuration files between formats and versions with environment variable extraction
Best use case
configuration-migrator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Migrate configuration files between formats and versions with environment variable extraction
Teams using configuration-migrator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/configuration-migrator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How configuration-migrator Compares
| Feature / Agent | configuration-migrator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Migrate configuration files between formats and versions with environment variable extraction
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 modernizationRelated Skills
lms-configuration-administration
Configure learning management system settings, user roles, course templates, gradebooks, and third-party integrations
ui-component-migrator
Migrate UI components between frameworks with structure, state, and style transformation
logging-migrator
Migrate logging infrastructure with format standardization, structured logging, and aggregation setup
event-sourcing-migrator
Migrate to event-sourcing architecture with event extraction, store setup, and CQRS implementation
build-system-migrator
Migrate build systems to modern alternatives with build file conversion and CI/CD integration
authentication-migrator
Migrate authentication systems with credential migration, OAuth2/OIDC setup, and identity provider integration
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.