AgentKit
ReferenceCLI commands
BetaYou are reading docs for the beta channel (2.4.1-beta.1) — updated automatically on every beta release.Switch to stable →

CLI commands

ak kit install

Install a kit into the current project or adapter user directory

ak kit install loads a kit (such as engineer or marketing) and emits its agents, skills, and commands through one or more target adapters. By default it writes runtime-native project content; --switch-to-plugin selects a Claude Code project plugin instead, and --build-only writes the output without installing it.

When to use it: Run it once ak licenses confirms access to a paid kit and you want the kit's agents, skills, and commands available locally for adapters like Claude Code and Codex. Use --target to choose adapters, --skills / --exclude-skills to control which skills install, and --global to install into the adapter user directory rather than the current project.

Project-native mode merges AgentKit-owned resources into ./.claude and stores lifecycle metadata under ./.agentkit, preserving unknown and user-modified files. --force authorizes a tracked overwrite after taking a snapshot.

Usage

ak kit install <kit-name> [flags]

Examples

ak kit init engineer --yes --no-interactive # remote registry is the release default
ak kit init engineer --local --kits-dir kits/ --yes # dev/CI explicit source
ak kit init engineer --target claude-code                    # entitled project-native Claude Code install
ak kit init engineer --remote --target claude-code --switch-to-plugin # entitled Claude Code project plugin
ak kit init engineer --remote --target codex                     # authenticated Codex project install
ak kit init engineer --remote --target codex --global            # install under ~/.codex
ak kit install engineer --skills ak-cook,ak-plan --yes  # install selected skills
ak kit install engineer --exclude-skills ak-video --yes # exclude selected skills
ak kit init engineer --remote --switch-to-plugin --yes --json --no-interactive # scripted project install
ak kit init engineer --local --kits-dir kits/ --global --yes --no-interactive # native install from explicit source
ak kit init engineer --local --kits-dir kits/ --target claude-code --yes # project-native install from explicit source
ak kit init engineer --kits-dir kits/ --build-only --out /tmp/out --json # local development build

Flags

FlagDescription
--build-onlyBuild plugin to a local directory instead of installing
--channel stringRemote registry channel (beta requires explicit opt-in) (default "stable")
--exclude-skills stringComma-separated skill names to skip while installing the rest of the kit
--forceOverwrite existing output directory
-g, --globalInstall into the adapter user directory instead of the current project
-h, --helphelp for install
--jsonEmit machine-readable JSON (implies --no-interactive)
--kits-dir stringExplicit local kits directory for --local or local build development
--localInstall from an explicit --kits-dir or AGENTKIT_KITS_DIR source instead of the remote registry (dev/CI)
--no-backupSkip the pre-install snapshot + ClaudeKit takeover on a global install (power users only — leaves CK content active)
--no-interactiveDisable interactive prompts (CI-safe)
--out stringOutput root directory (requires --build-only)
-q, --quietSuppress non-error output on stderr
--registry-url stringAgentKit registry base URL (default: $AGENTKIT_REGISTRY_URL, then dev/staging https://staging.agentkit.best or release https://agentkit.best)
--remoteInstall from the authenticated remote registry (default; explicit use will be deprecated soon) (default true)
--select-skillsInteractively choose kit skills before install
--skills stringComma-separated skill names to install from the kit
--switch-to-pluginExplicitly select Claude Code project plugin mode (and replace native mode when present)
--target stringEmitter target ID or comma-separated IDs (e.g. claude-code,codex) (default "claude-code")
-V, --verboseExtra diagnostic output on stderr (loses to --quiet)
--version stringRemote kit version (defaults to channel latest)
-y, --yesAssume yes for all prompts

Output modes

ModeBehavior
prettydefault on TTY (colors, ASCII markers)
plainauto when stdout piped or --no-interactive
json--json (single-object envelope, NDJSON-safe)

Exit codes

CodeMeaning
0success
1runtime error
2invalid flags
3user-cancel (SIGINT, prompt-cancel)
5kit not found in --kits-dir
6target directory exists without --force
  • ak kit — Kit management commands

On this page