claude-loadout

Claude Loadout

Share your Claude Code setup like dotfiles.

A Claude Code plugin that bundles your CLAUDE.md, skills, slash commands, and sub-agents into a portable loadout any other Claude Code user can install with one command.

---

The pitch

Every Claude Code user gradually shapes their workflow with a personal mix of CLAUDE.md rules, custom skills, slash commands, and sub-agents. Today there is no standard way to share that. Devs end up emailing snippets, screenshotting setups, or copy-pasting skill files into Slack.

Claude Loadout treats your config like a gamer's loadout: a complete equipped set of gear you can publish once and let any teammate adopt — without disturbing their own gear.

# Bundle your setup
claude-loadout export --name py-data-eng --description "Python + dbt + Snowflake setup"

# Push it to GitHub. A teammate then runs:
claude-loadout install jane/py-data-eng

# Their Claude now has @jane/snowflake-explain, @jane/dbt-debug, @jane/data-reviewer
# — namespaced under @jane so their own setup is untouched.

---

How it works

The pipeline is six stages, from author to adopters:

1. Your Claude Code config — CLAUDE.md, skills, commands, sub-agents.
2. Export — bundled into a directory with a validated profile.json manifest.
3. Sanitize — scans the bundle for secrets, absolute home paths, and *_KEY= style assignments.
4. Git push — the bundle becomes a public (or private) repo on GitHub / GitLab / anywhere with Git.
5. Install — anyone runs claude-loadout install owner/repo to fetch and validate it.
6. Adopters — the loadout's items appear under @author/... in their Claude Code session, namespaced so nothing of their own is overwritten.

On the adopter's disk, an installed loadout looks like this:

~/.claude-loadout/jane-py-data-eng/
   skills/snowflake-explain/SKILL.md
   commands/dbt-debug.md
   agents/data-reviewer.md
   CLAUDE.md
   profile.json    ← validated manifest
   .install.json   ← source, ref, install date

---

Install in Claude Code

Run these two commands inside any Claude Code session:

/plugin marketplace add TusharKarkera22/claude-loadout
/plugin install claude-loadout@claude-loadout

The first line registers this repo as a one-plugin marketplace, the second installs the plugin from it. After that, /loadout export, /loadout install, and the rest are available as native slash commands.

Plugins can run code on your machine. Read SECURITY.md before installing anything from a stranger.

---

Quickstart (clone-and-build, for hacking on the source)

# 1. Setup
git clone https://github.com/TusharKarkera22/claude-loadout.git && cd claude-loadout
npm install
npm run build

# 2. Bundle your current Claude Code config
node dist/cli.js export \
  --source . \
  --out  ./my-loadout \
  --name my-loadout \
  --description "Tushar's Azure data-eng workflow" \
  --author your-github-handle

# 3. (Optional) Re-scan an existing loadout for secrets
node dist/cli.js sanitize ./my-loadout

# 4. Push it
cd my-loadout && git init && git add . && git commit -m "Initial loadout" && \
  gh repo create your-handle/my-loadout --public --source=. --push

# 5. A teammate installs it
node dist/cli.js install your-handle/my-loadout

# 6. Manage installed loadouts
node dist/cli.js list
node dist/cli.js show   your-handle-my-loadout
node dist/cli.js update your-handle-my-loadout
node dist/cli.js remove your-handle-my-loadout

After npm link (or once published) the binary is exposed as claude-loadout, so the same flows become claude-loadout export …, claude-loadout install …, etc.

The same operations are exposed as /loadout * slash commands once the plugin is loaded into Claude Code.

---

Subcommand reference