claude-kits

One-command installer for Claude Code kits.

npx claude-kits-cli add growth-team

That single command validates your license, installs the kit's agents / skills / commands into ~/.claude (available in every project), scaffolds the kit's per-project config into the current repo, and wires the @import so Claude Code loads it automatically.

Commands

| Command | What it does | |---|---| | claude-kits add <kit> | Install a kit (prompts for a license key if paid) + scaffold project config. | | claude-kits init <kit> | Re-scaffold an already-installed kit's config into the current project. | | claude-kits list | List available and installed kits. | | claude-kits update <kit> | Re-fetch and reinstall the latest version (reuses the stored key). | | claude-kits remove <kit> | Delete exactly the files a kit installed (leaves your config). |

Flags: --key <key> (skip the prompt), --scope user|project (default user).

How it works

• Install scope. Kit content goes to ~/.claude by default so agents and commands work across all your projects. Per-project config (e.g. CLAUDE.growth.md) is scaffolded into the project you run add in.
• Clean install/remove. Every file written is recorded in a manifest under ~/.claude/.claude-kits/<kit>.json, so remove and update touch only what the kit added and prune emptied directories.
• Licensing. Free kits install directly. Paid kits validate the key against the license API, which returns a short-lived signed download URL — the key never grants raw repo access.

Environment variables

| Var | Purpose | |---|---| | CLAUDE_KITS_DEV=1 | Install from the local monorepo, skipping license + download. For kit development. | | CLAUDE_KITS_LICENSE_API | Base URL of the license-validation endpoint. Required to install paid kits (unless dev). | | CLAUDE_KITS_LICENSE | Fallback license key (otherwise prompted / read from the local store). | | CLAUDE_KITS_REGISTRY_URL | Hosted registry URL so new kits appear without a CLI upgrade. Falls back to the bundled registry.json. | | CLAUDE_KITS_REPO | Override the monorepo root used in dev mode. | | CLAUDE_CONFIG_DIR | Standard Claude Code override for the user config dir (honored here too). |

Adding a kit to the registry

Kits are declared in src/registry.json. A kit maps its id to a source directory and (optionally) a per-project config file with the @import target and the sections a user must fill in before it works.

Development

npm install
CLAUDE_KITS_DEV=1 node bin/claude-kits.js list

Server pieces are stubbed but wired: the license API contract (POST /v1/licenses/validate → { valid, downloadUrl, version }) and the signed-tarball download path exist and are exercised in production; dev mode reads kit files straight from this repo.