claude-sync-kit

Cross-device sync for your Claude Code setup. A wizard skill that walks you through creating a private GitHub repo that mirrors your ~/.claude/ configuration across machines — settings, custom skills, plugin/MCP enablement — without ever committing your auth token.

Distributed as a Claude Code plugin via its own marketplace.

What this is

A single-skill Claude Code plugin. After you install it, ask Claude something like:

• "Sync my Claude Code setup to my laptop."
• "Get the same Claude config on a new machine."
• "Mirror my plugins and skills between PC and laptop."

The cross-device-sync skill activates and walks you through:

1. Choosing scope — what gets synced (settings, custom skills, CLI

inventory) and what stays per-device (auth tokens, sessions, memory, plans, runtime state).

1. Creating a private repo — via gh repo create --private.
2. Scaffolding the repo — .gitignore, bootstrap, prereqs,

push-from-machine, plus a per-MCP re-auth guide.

1. A security gate before first push — git ls-files check for

credentials, .env, OAuth, Python build artifacts.

1. The second-machine workflow — prereqs → login → bootstrap →

restart → re-authenticate connectors on first use.

The repo it creates is yours. This plugin doesn't host anything centrally and doesn't phone home.

Install

/plugin marketplace add Fluory/claude-sync-kit
/plugin install claude-sync-kit

Then start a conversation and ask Claude to sync your setup.

What gets synced

The bundled .gitignore covers all of this.

Why a wizard, not a CLI

A static template repo would force you into one structure. The wizard:

• Detects your OS on both machines (Windows-first; Mac/Linux templates

best-effort).

• Picks up where your real skill content lives (junctions on Windows,

symlinks on Unix often resolve to a separate skills directory).

• Generates only the scripts and gitignore entries you actually need.
• Runs the security gate as part of the flow, not as an opt-in.

You can also just lift the templates from skills/cross-device-sync/templates/ and use them directly without Claude in the loop.

What this is NOT

• Memory sync. claude-mem per-project memory is intentionally

out of scope. It's per-project, per-device, conflict-prone.

• A public skill marketplace. This plugin helps you sync your own

setup; it doesn't help you redistribute downloaded third-party skills.

• A backup tool. No history, no encryption. It's a configuration

mirror, not a vault.

Caveats

• Windows is the tested path. The author runs it on Windows; Mac/Linux

templates are reasonable but unverified. PRs welcome.

• Connectors re-auth per machine. This is on purpose — your Stripe

key on one laptop should not appear on another via a sync. If this annoys you, you're using the wrong tool.

• GitHub Secret Scanning will catch leaked Claude tokens even in

private repos and invalidate them. The .gitignore matters even when the repo is private. The skill enforces a pre-push check.

License

MIT. See LICENSE.

Author

@Fluory — Florian Hein.