migrating-sing-box-configs

Migrate sing-box configuration fields across versions 1.8.0 through 1.14.0.

629|22|Updated Nov 18, 2023
One-click install
npx skills add https://github.com/JohanChane/clashtui --skill migrating-sing-box-configs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-sing-box-configs
Source: https://github.com/JohanChane/clashtui/tree/main/.agents/skills/migrating-sing-box-configs
Command: npx skills add https://github.com/JohanChane/clashtui --skill migrating-sing-box-configs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents sing-box configuration breakage after upgrades by guiding version-by-version migrations and enforcing validation so deprecated or removed fields are handled correctly.

Core Features & Use Cases

  • Version-to-version migration playbook: Provides documented field migrations across sing-box versions from 1.8.0 through 1.14.0 (e.g., DNS rule changes, TLS certificate provider changes, outbound/inbound schema shifts).
  • Mandatory verification workflow: Ensures correctness by requiring sing-box check -c <config> after each migration step, treating failures as a stop-and-fix signal.
  • Fallback guidance for unknown cases: When a field/version transition isn’t covered, prompts for official documentation sources and fetches the relevant migration guide before recommending changes.

Quick Start

Run this skill to migrate your existing sing-box config between the exact source and target versions, and after each step execute sing-box check on the updated config until the check passes.

Frequently Asked Questions about migrating-sing-box-configs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate sing-box configs after upgrading to 1.14.0 breaks deprecated schemas?

Migrate sing-box configs safely by applying sequential, version-by-version field transformations for deprecated DNS rules and TLS ACME providers, then running `sing-box check -c <config>` after each step.

Why does sing-box configuration validation fail after a version upgrade?

Sing-box configuration validation fails after upgrades because older schemas are deprecated or removed, requiring field migrations across versions 1.8.0 through 1.14.0 to replace invalid DNS rules and WireGuard endpoint formats.

What is the best way to troubleshoot invalid sing-box config schemas across versions?

The best way to troubleshoot invalid sing-box schemas is using documentation-backed migration guides for unknown field transitions, applying stepwise transformations, and treating `sing-box check -c <config>` failures as a stop-and-fix signal.

Do I need to validate sing-box configs after each migration step?

Yes, you need to validate sing-box configs after each migration step by running `sing-box check -c <config>`, which is a mandatory verification workflow to ensure deprecated fields are handled correctly before proceeding.

Can I migrate sing-box DNS rules and TLS certificate providers between 1.8.0 and 1.14.0?

Yes, you can migrate sing-box DNS rules and TLS certificate providers by following a version-to-version migration playbook that applies sequential transformations for schema shifts across versions 1.8.0 through 1.14.0.