Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Configuration Migrator Skill · a5c-ai | DecimalAI

a5c-ai/configuration-migrator

SkillScore65Maintained

Migrate configuration files between formats and versions with environment variable extraction

DevOpsby a5c-ai

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

DevOps & SRE pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/a5c-ai-configuration-migrator/SKILL.md

decimalai skills pull a5c-ai-configuration-migrator --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/a5c-ai-configuration-migrator/SKILL.md https://app.decimal.ai/s/a5c-ai-configuration-migrator/SKILL.md

Raw file: /s/a5c-ai-configuration-migrator/SKILL.md ↗ · machine-readable summary at /s/a5c-ai-configuration-migrator.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

23 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 58d ago

Yes — +52% lift-16% tokens0% turns65% of whole cases pass with skill (15/23)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	11%	0%
case-02	✗→✓	▲ Improved	66%	0%
case-03	✗→✓	▲ Improved	-6%	0%
case-09	✗→✓	▲ Improved	-57%	0%
case-12	✗→✓	▲ Improved	-68%	0%

Showing 5 of 23 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 7/31/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

a5c-ai / babysitter

library/specializations/code-migration-modernization/skills/configuration-migrator/SKILL.md

View on GitHub ↗

License MITImported 7/31/2026Version v1

Skill contents

SKILL.md

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

Illustrative Want to see what a5c-ai/configuration-migrator would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/1/2026, 01:35 UTC · 23 cases

Lift

+52%

65% vs 13%

Agent turns

0%

1.0 vs 1.0

Tokens

-16%

1,811.22 vs 2,164.61

fail → pass · 12pass → pass · 3fail → fail · 8

Per-case results (23)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 I need to transform my legacy configuration file at `/services/payment/config.properties` into YAML format at `/services/payment/config.yaml`. Please pull out any hardcoded credentials or API tokens so they are replaced by environment variable references. Provide a structured migration report in JSON that includes the migration ID, source and target file details, key conversion maps, extracted environment variables and secrets, plus any schema validation errors or warnings.	fail→pass	11,425	14,364	+26%	1	1	0%	2,935	3,261	+11%	0	0	—
case-02 We are converting `/opt/app/settings.ini` to `/opt/app/settings.json`. During this refactor, scan for any sensitive keys or hardcoded passwords, move them into external environment variables, and validate the final JSON structure against our standard schema. Give me the result formatted as a JSON object containing source and target metadata, key transformation steps, extracted secret/variable lists, and validation status with any errors or warnings.	fail→pass	8,816	10,843	+23%	1	1	0%	1,926	3,196	+66%	0	0	—
case-03 Can you convert the legacy XML configuration at `/etc/web/app.xml` into a JSON configuration file located at `/etc/web/app.json`? Please identify environment-specific values to pull into a dotenv template, check for hardcoded API keys, and run schema validation. Output the complete migration summary in JSON detailing the file paths, conversion array, extracted items, and validation outcome.	fail→pass	13,775	10,267	-25%	1	1	0%	3,198	3,004	-6%	0	0	—
case-04 We converted our application configuration to YAML. Now we need to deploy a Kubernetes StatefulSet using Helm and apply these configurations directly into the live cluster pod environment. Can you write the kubectl and helm deployment commands to roll this out to the production cluster?	fail→fail	9,236	6,395	-31%	1	1	0%	1,878	1,779	-5%	0	0	—
case-05 We migrated `db.properties` to `db.yaml`. Now, please rewrite our Java `ApplicationConfig.java` source code file to replace the `java.util.Properties` file loading logic with Jackson YAML parsing code.	pass→pass	23,988	8,314	-65%	1	1	0%	2,613	2,596	-1%	0	0	—
case-06 We need to migrate our relational database tables from PostgreSQL to MySQL. Generate the SQL DDL statements to convert table schemas, indexes, foreign keys, and sequence definitions.	fail→fail	14,865	25,110	+69%	1	1	0%	3,225	5,119	+59%	0	0	—
case-07 When processing and transforming YAML configuration files via command-line scripting in automated migration pipelines, which CLI tool should be integrated?	fail→fail	10,317	2,726	-74%	1	1	0%	1,944	1,058	-46%	0	0	—
case-08 Which CLI utility should be integrated for parsing, filtering, and manipulating JSON config files in automated migration scripts?	fail→fail	8,736	2,022	-77%	1	1	0%	1,647	909	-45%	0	0	—
case-09 Which CLI tool should be integrated into the migration toolchain specifically for secret detection and preventing hardcoded credentials from entering git repositories?	fail→pass	10,579	2,594	-75%	1	1	0%	2,017	870	-57%	0	0	—
case-10 Which tool or library is specified in the integration architecture for parsing and handling ENV files during variable extraction?	fail→fail	4,800	2,000	-58%	1	1	0%	632	820	+30%	0	0	—
case-11 When reporting migration results using the standard migration output schema, what is the exact string format specified for the 'timestamp' key?	fail→fail	6,762	1,626	-76%	1	1	0%	1,208	776	-36%	0	0	—
case-12 In the standard configuration migration JSON report, what are the exact key names required inside each object in the 'conversions' array?	fail→pass	15,325	2,059	-87%	1	1	0%	2,977	939	-68%	0	0	—
case-13 In the standard migration report JSON structure, what are the two required array properties contained inside the top-level 'extracted' object?	fail→pass	12,662	2,158	-83%	1	1	0%	2,391	868	-64%	0	0	—
case-14 What three properties must be present inside the 'validation' object of the standard migration output JSON report?	fail→pass	15,469	2,396	-85%	1	1	0%	2,175	862	-60%	0	0	—
case-15 Which related skill is designated for handling secret compliance checks alongside configuration migrations?	fail→pass	7,046	1,515	-78%	1	1	0%	1,310	732	-44%	0	0	—
case-16 Which agent is designated for configuration modernization tasks in conjunction with configuration migration?	fail→pass	16,894	1,504	-91%	1	1	0%	2,173	707	-67%	0	0	—
case-17 Convert `/configs/database.properties` containing `db.host=localhost` and `db.port=5432` to YAML at `/configs/database.yaml`, extract any credentials into `.env`, and output the JSON report matching the migration output schema.	fail→pass	9,212	8,283	-10%	1	1	0%	1,758	2,179	+24%	0	0	—
case-18 We are migrating `/etc/app/config.ini` to `/etc/app/config.json`. Generate the migration summary report adhering to the standard JSON migration schema with source and target formats, conversion mappings, and validation results.	fail→pass	11,205	5,875	-48%	1	1	0%	2,139	1,933	-10%	0	0	—
case-19 We have a configuration at `/app/settings.toml` that needs conversion to JSON at `/app/settings.json`. Output the migration summary conforming to the official output schema.	fail→pass	18,411	9,217	-50%	1	1	0%	3,401	2,526	-26%	0	0	—
case-20 Migrate `/etc/service/config.xml` to `/etc/service/config.yaml`. Extract environment-specific values and output the standard migration JSON schema.	pass→pass	11,496	11,062	-4%	1	1	0%	2,486	3,198	+29%	0	0	—
case-21 In which migration process context is configuration version updating typically integrated when upgrading framework dependencies?	fail→fail	11,184	2,376	-79%	1	1	0%	1,682	871	-48%	0	0	—
case-22 Which migration process handles cloud configuration adaptation during infrastructure shifts?	fail→fail	10,387	1,801	-83%	1	1	0%	1,439	760	-47%	0	0	—
case-23 How does the configuration migration process handle missing or default values when converting legacy configurations?	pass→pass	15,378	12,617	-18%	1	1	0%	2,632	2,695	+2%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +52 percentage points is the difference between those two pass rates over the 23 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 13%
Pass rate with the skill: 65.2%
Cases attempted: 23
Cases counted toward lift: 23
Cases that regressed: 0
Skill version measured: v1
Run completed: 8/1/2026, 01:35 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

I need to transform my legacy configuration file at `/services/payment/config.properties` into YAML format at `/services/payment/config.yaml`. Please pull out any hardcoded credentials or API tokens so they are replaced by environment variable references. Provide a structured migration report in JSON that includes the migration ID, source and target file details, key conversion maps, extracted environment variables and secrets, plus any schema validation errors or warnings.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run65

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+10% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 57 days ago

Other measured skills in the registry, with their headline benchmark lift.