Ark310

Claude Config Transfer — Development skill for Claude Code

Development community

Two PowerShell scripts that move a full Claude Code setup (settings, permissions, personal skills, all marketplace plugins) to another Windows machine: secrets blanked, hooks dropped, backups made, an.

How to install Claude Config Transfer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Ark310/claude-config-transfer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Config Transfer does

Alternatives in Development

Connect — Fancy stream processing made operationally mundane 8608 114 1 8.6k ★
Memory Gc — Inspect or rotate the autopilot ledger JSONL files (findings.jsonl, negatives.jsonl) 3.8k ★
X Mentor Skill — X导师.skill — 女娲的第一个「非人类」作品 1.2k ★

README

Claude Config Transfer

Move a whole Claude Code setup (settings, permission allow-list, personal skills and every installed plugin) to another Windows machine with two PowerShell scripts. It never copies credentials.

![PowerShell](https://img.shields.io/badge/PowerShell-5.1+-5391FE?logo=powershell&logoColor=white) ![Platform](https://img.shields.io/badge/platform-Windows-0078d6?logo=windows) ![Claude Code](https://img.shields.io/badge/for-Claude%20Code-d97757?logo=anthropic) ![License](https://img.shields.io/badge/license-MIT-green) ![Built with Claude Code](https://img.shields.io/badge/Built%20with-Claude%20Code-d97757?logo=anthropic)

🧭 Part of **Abdul Raqeeb Khatri's portfolio**: [📂 Hub](https://github.com/Ark310/portfolio) · [🌐 Site](https://ark310.github.io) · [💼 Experience](https://github.com/Ark310/experience)

Overview

Rebuilding a tuned Claude Code environment by hand on a new machine (model and effort defaults, theme, a long permission allow-list, a dozen marketplace plugins, personal skills) takes a while and is easy to get wrong. Copying `~/.claude` wholesale is worse: it carries your OAuth token, chat history and hooks that point at apps the new machine doesn't have, and the plugin registry is full of absolute paths from the old home folder.

This repo is the two-script answer. **Export** builds a sanitized `payload\` on the source machine. **Import** installs it on the target, backs up anything it replaces, and rewrites the old home path everywhere it appears.

💡 Why I Built It

Rebuilding a tuned Claude Code environment by hand takes a while and is easy to get wrong, and copying the folder wholesale would carry OAuth tokens and broken absolute paths.

📈 Impact

Two scripts move a full setup: 14 plugins, about 2,300 files.
Credentials and account state are deliberately excluded, and old home-folder paths are rewritten everywhere.