Import config
Reverse-engineer an existing hand-maintained AI config (Claude Code / Copilot / OpenCode / VS Code) into an agentsync config/, then prove nothing is lost. Use to migrate onto agentsync without rebuilding config by hand.From its SKILL.md
npx -y skills add RachidChabane/agentsync --skill import-configAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, 622 tokens by cl100k_base, as published. Nobody here has run it
Import an existing config into agentsync
Turning a live, hand-built setup into a config/ is judgment (dedup, decide what's
core vs passthrough, find skill sources) made safe by a deterministic diff-proof. Do
not switch the user's real config until diff-prove.sh is clean.
1. Read the live config (resolve symlinks to the real source)
- Claude —
~/.claude/settings.json,~/.claude/CLAUDE.md(follow@imports), MCP viaclaude mcp list/~/.claude.json, skills in~/.claude/skills/(note where each symlinks to — that's its source). - Copilot —
~/.copilot/{settings.json, mcp-config.json, copilot-instructions.md},~/.copilot/skills/. - OpenCode —
~/.config/opencode/opencode.json. - VS Code —
Code/User/settings.json(instructions + hook locations).
2. Synthesize config/ (the judgment)
instructions.md— the shared instruction text (merge per-tool variants into one).skills.json— tier per skill (fromskillOverrides/disabledSkills/permission.skill). Where a skill dir symlinks to a real source, recordsource(+subpath) so agentsync manages it; for git-backed skill repos use the git URL.mcp.json— the union of MCP servers across tools, deduped by identity (same server defined per-tool collapses to one). Mark secret-bearing ones withauth.profile.json— the harnesses in use.overrides.json— everything agentsync's four core concerns don't cover but the live config sets: plugins/marketplaces, status line, model effort, custom notification hooks (underhooks, merged additively), editor prefs. This catches what would otherwise be lost.
3. Prove nothing is lost (deterministic — required)
bash skills/import-config/diff-prove.sh
It applies config/ into a sandbox seeded with the live files and diffs the result
against the originals. Iterate config/ until it prints CLEAN. A DIFF means a key
or hook the live config has isn't reproduced — usually something to add to
overrides.json. Don't proceed on any unexplained diff.
4. Only then switch
With a clean diff-proof, the real agentsync apply is safe — every change it would make
is already accounted for. Keep the old config repo as rollback until you've run a session
in each harness. agentsync uninstall reverts agentsync's changes if needed.
What ships with it: 1 file
3.5 KB alongside SKILL.md, 1 of them executable
- diff-prove.shruns3.5 KB