claude-pack

Portable Claude Code setup — installs your plugins, skills, MCP servers, and settings on any machine with a single command.

Installation

From npm

npx claude-code-pack install

Or install globally:

npm install -g claude-code-pack
claude-pack install

From GitHub

git clone [email protected]:lvtan71/claude-pack.git
cd claude-pack
npm link
claude-pack install

Or run directly without installing:

npx github:lvtan71/claude-pack install

What It Does

claude-pack reads claude-pack.config.json and sets up your Claude Code environment:

| Component | How it installs | |-----------|----------------| | Plugins | Clones from GitHub, registers in ~/.claude/plugins/ | | Skills | Copies bundled skills or clones from GitHub to ~/.claude/skills/ | | MCP Servers | Merges config into ~/.claude/settings.json | | Settings | Merges model, statusline, and other preferences |

Everything is fetched fresh from GitHub, so you always get the latest version.

What's Included

Plugins

| Plugin | Source | Description | |--------|--------|-------------| | claude-mem | thedotmack/claude-mem | Persistent cross-session memory, smart code exploration (AST-based), phased implementation plans, and timeline reports | | understand-anything | Lum1104/Understand-Anything | Codebase analysis, interactive knowledge graphs, architecture visualization, onboarding guides, and diff analysis |

Marketplaces

| Marketplace | Source | Description | |-------------|--------|-------------| | thedotmack | thedotmack/claude-mem | Plugin marketplace for claude-mem and related tools | | understand-anything | Lum1104/Understand-Anything | Codebase understanding, onboarding, and architecture analysis tools |

Skills (Bundled)

| Skill | Description | |-------|-------------| | cloud-devops | Cloud infrastructure and DevOps workflows — AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring | | fastapi | FastAPI best practices, Pydantic models, dependency injection, streaming, and latest patterns | | senior-ml-engineer | MLOps pipelines, model deployment, drift monitoring, RAG systems, LLM integration, cost optimization | | technical-writer | Documentation, API references, guides, tutorials, and technical content creation |

MCP Servers

| Server | Type | Source | Description | |--------|------|--------|-------------| | linear | HTTP | mcp.linear.app | Linear project management — issues, projects, comments, milestones | | context7 | HTTP | mcp.context7.com | Up-to-date library documentation and code examples | | fetch | stdio | mcp-server-fetch (uvx) | Fetch web content for processing | | filesystem | stdio | @modelcontextprotocol/server-filesystem (npx) | File system access (defaults to $HOME, configurable at install) | | sequential-thinking | stdio | @modelcontextprotocol/server-sequential-thinking (npx) | Step-by-step reasoning and problem decomposition | | time | stdio | mcp-server-time (uvx) | Current time and timezone operations |

$HOME in MCP server args is automatically resolved to the user's home directory at install time. The filesystem server prompts you during install to confirm or customize the path. Works on Linux/WSL, macOS, and Windows.

Settings

| Setting | Value | |---------|-------| | Model (Claude Code) | opus | | Model (Codex) | gpt-5.4 (reasoning effort: xhigh) | | Statusline | Custom bash script with context window, 5h/7d rate limit bars, and color-coded usage indicators |

Codex Integration

The installer also generates a ~/.codex/config.toml that reuses the same MCP servers and skills as Claude Code — no duplicate configuration needed.

| What | How it works | |------|-------------| | MCP servers | Generated into config.toml from the same mcpServers in claude-pack.config.json | | Skills | Installed to both ~/.claude/skills/ (Claude Code) and ~/.codex/skills/ (Codex) from the same bundled source |

This means when you add a new MCP server or skill to the pack, both Claude Code and Codex pick it up.

Commands

claude-pack install          # Install everything
claude-pack status           # Dry run — show what would be installed
claude-pack help             # Show help

# Flags
claude-pack install --force         # Overwrite existing installations
claude-pack install --skip-plugins  # Skip plugin installation
claude-pack install --skip-skills   # Skip skill installation
claude-pack install --skip-settings # Skip settings merge
claude-pack install --skip-codex    # Skip Codex config generation
claude-pack install --dry-run       # Preview without changes

Contributing

Setup

git clone [email protected]:lvtan71/claude-pack.git
cd claude-pack
npm link    # makes `claude-pack` command available locally

Adding a Plugin

1. Edit claude-pack.config.json — add entries to both plugins and marketplaces:

// In "plugins" array:
{
  "name": "my-plugin",
  "marketplace": "marketplace-name",
  "repo": "github-user/repo-name",
  "enabled": true
}

// In "marketplaces" array:
{
  "name": "marketplace-name",
  "repo": "github-user/repo-name"
}

2. Update the Plugins and Marketplaces tables in this README.

Adding a Skill

Option A — Bundled skill (skill files live in this repo):

1. Create skills/my-skill/SKILL.md (and optional references/ directory).
2. Add to claude-pack.config.json:

{ "name": "my-skill", "source": "bundled" }

Option B — GitHub-hosted skill (cloned at install time):

1. Add to claude-pack.config.json:

{ "name": "my-skill", "source": "github", "repo": "github-user/my-skill-repo" }

2. Update the Skills table in this README.

Adding an MCP Server

1. Add to the mcpServers object in claude-pack.config.json:

"mcpServers": {
  "server-name": {
    "command": "npx",
    "args": ["-y", "@scope/mcp-server"]
  }
}

2. Update the MCP Servers section in this README.

Publishing a New Version

1. Make your changes and commit.
2. Bump the version:

npm version patch   # 1.0.0 → 1.0.1 (bug fixes, small updates)
npm version minor   # 1.0.0 → 1.1.0 (new plugins/skills added)
npm version major   # 1.0.0 → 2.0.0 (breaking config changes)

3. Push with tags:

git push origin main --tags

4. Publish to npm:

npm publish

npm version automatically creates a git commit and tag (e.g., v1.1.0). Make sure all changes are committed before running it.

Pull Request Guidelines

• One plugin/skill/MCP server per PR when possible.
• Update the README tables to reflect your additions.
• Test with claude-pack install --dry-run before submitting.
• Test a full install with claude-pack install --force on a clean environment if possible.

Requirements

• Node.js >= 18
• git

License

MIT