Your AI coding agent only knows what you teach it. Without guidance it writes generic, unidiomatic code, pushes straight to main, and runs rm -rf on things you liked. Hand-configuring skills, hooks and agents takes hours — so nobody ever does it.

kimi-boost installs a complete, opinionated development workflow in seconds:

GIF won't load (or you're behind a slow CDN)? Same session, as plain text:

$ kimi-boost install vue3
✓ [kimi] Installed preset 'vue3' into Kimi Code
  /Users/you/.kimi-boost/hooks/vue3
  config.toml[extra_skill_dirs], config.toml[extra_agent_dirs], config.toml[[hooks]] (+1)
  Run /reload or start a new session.

$ kimi-boost doctor
✓ kimi: detected (version 0.36.1)
✓ kimi: config.toml parses
✓ kimi: hook script valid
✓ kimi: mounted dir present
All checks passed.

① Official Kimi Code plugin channel — no CLI required. The five flagship presets are mirrored to single-plugin repos and install natively:

/plugins install https://github.com/shidesheng0218/kimi-boost-vue3

Available mirrors: vue3 · react · go · python · usage

Or browse them inside the /plugins panel via our marketplace feed:

export KIMI_CODE_PLUGIN_MARKETPLACE_URL=https://raw.githubusercontent.com/shidesheng0218/kimi-boost/main/marketplace.json

② kimi-boost CLI — all 19 presets, three harnesses. One installer for Kimi Code, Claude Code and Codex CLI, with updates, doctor checks and clean uninstalls:

npx kimi-boost install

Special presets:

Every preset bundles a best-practice SKILL.md (auto-loaded) + a reviewer agent. New stacks are vote-driven — issue #1. "via CLI" presets get their own official repo as demand grows.

Each preset is one directory in this repo — a valid kimi.plugin.json plugin AND a kimi-boost preset. Contributions welcome:

presets/<id>/
├── preset.json          # kimi-boost metadata
├── kimi.plugin.json     # Kimi Code plugin manifest (native marketplace form)
├── skills/<name>/SKILL.md
├── agents/<name>-reviewer.md
└── hooks/<name>.mjs     # cross-platform Node, fail-open by design

kimi-boost install <preset> --project writes the preset into the current project instead of your user config:

• skills → .agents/skills/ (Kimi Code + the cross-tool .agents/ convention) and .claude/skills/
• agents → .agents/agents/ and .claude/agents/
• hooks → .claude/settings.json (Claude Code only — Kimi Code has no project-level hook mechanism; Codex is skipped)

Everything lands inside the project root (nearest .git ancestor), so you can commit the preset and share it with your team — every clone gets the same AI behavior. Remove with kimi-boost remove <preset> --project.

Anyone can publish a preset as a plain GitHub repo (a preset.json at the repo root, plus skills/, agents/, hooks/):

kimi-boost install github:owner/repo          # or the full https://github.com/owner/repo URL
kimi-boost install github:owner/repo@v1.2.0   # pin a branch or tag

kimi-boost shows you exactly what the preset will register — especially its hooks, which execute when the agent runs — and asks for confirmation before installing (--yes to skip in scripts, --dry-run to preview). Community presets are tracked in update / outdated against their source repo, so they stay current. Only install presets from authors you trust — hooks run shell commands with your agent's permissions.

The usage preset quietly counts your sessions / prompts / tool calls. stats turns it into a report you'll want to screenshot:

$ kimi-boost stats -d 7
📊 kimi-boost stats · last 7 days

  128 prompts  ·  12 sessions  ·  856 tool calls  ·  5 active days  ·  streak 3 🔥

09-01 ████████████ 24
09-02 ██████ 12
...

$ kimi-boost stats --share   # → kimi-boost-stats.svg

--share exports a self-contained SVG card (no server, no upload — your data never leaves your machine). Post it, or embed it in your README next to a kimi-boost badge.

Most "agent safety" is invisible — a hook silently blocks something and you never know your agent almost ran rm -rf /. kimi-boost makes the seatbelt visible:

• Every blocked action is logged to ~/.kimi-boost/guard-log.jsonl (secret previews are redacted — never the secret itself).
• kimi-boost guard shows every guard's status and how many times it fired; guard --log lists recent blocks with timestamps.
• kimi-boost stats reports 🛡️ N blocks — your share card can now say "it stopped my agent N times this week."
• Tune live without reinstalling: guard --disable <name> / --enable <name>, or teach block-dangerous your own patterns with guard --add-pattern <regex>.

The core preset now also shields credential files (~/.ssh, ~/.aws/credentials, *.pem…) from being read into the model's context, and blocks workspace-destroying git ops (reset --hard, clean -f, checkout -- .).

export captures your whole kimi-boost setup — installed presets with versions, community preset sources, and the background update check — into one shareable file:

kimi-boost export                          # → kimi-boost-export.json
kimi-boost export --embed-content          # → .tar.gz with preset contents (exact, offline)
kimi-boost export --include-usage          # also carry your usage history

# on the new machine:
kimi-boost import kimi-boost-export.json   # shows the plan, asks once, restores everything
kimi-boost import kimi-boost-export.json --dry-run

Official presets reinstall from the registry, community presets reinstall from their exact repo@ref source, and the update watch is re-registered. Commit the file to your dotfiles repo, or drop it in your team's chat — one file, same AI workflow everywhere.

Building a community preset? Three helpers cover the loop:

kimi-boost validate ./my-preset   # schema, hooks, skills, plugin manifest
kimi-boost dev ./my-preset        # validate + preview the install (dry-run)
kimi-boost package ./my-preset    # validate + pack my-preset-1.0.0.zip

Push the directory to a GitHub repo (with preset.json at its root) and anyone can install it with kimi-boost install github:you/my-preset.

$ kimi-boost doctor
✓ kimi: detected
  version 0.36.1
✓ kimi: config.toml parses
✓ kimi: hook script valid
  /Users/you/.kimi-boost/hooks/vue3/protect-main.mjs
✓ kimi: mounted dir present
⚠ codex: CLI not detected
  Install codex or ignore if you don't use it.

1 warning(s), no errors

kimi-boost doctor --fix restores missing mounted dirs and hook scripts automatically.

flowchart TD
    REG["<b>presets/ registry</b> (19 presets)<br/>skills · agents · hooks · mcp"]

    subgraph CI["Monorepo CI"]
      VERIFY["verify.yml<br/>live-installs every preset<br/>into a real Kimi Code CLI"]
      SPLIT["split-presets.yml<br/>git subtree mirror"]
    end

    REG --> CI
    SPLIT -->|"auto-mirror"| M1["kimi-boost-vue3"]
    SPLIT -->|"auto-mirror"| M2["react · go · python · usage"]
    M1 & M2 -->|"/plugins install"| KP["Kimi Code /plugins"]
    REG -->|"builds (repo sources)"| MKT["marketplace.json"]
    MKT -->|"KIMI_CODE_PLUGIN_MARKETPLACE_URL"| KP

    KB["<b>kimi-boost CLI</b><br/><i>install · remove · doctor · update</i>"]
    REG --> KB
    KB -->|"text-level edit"| KCF["~/.kimi-code/config.toml"]
    KB -->|"manifest-driven"| CCS["~/.claude/settings.json"]
    KB -->|"manifest-driven"| CXC["~/.codex/config.toml"]

    classDef cli fill:#7c3aed,color:#fff,font-weight:bold;
    classDef tool fill:#1e293b,color:#e2e8f0;
    classDef out fill:#064e3b,color:#a7f3d0;
    class KB,REG cli;
    class M1,M2,MKT tool;
    class KCF,CCS,CXC,KP out;

• Single source of truth — presets live in this monorepo; the five flagship mirrors are read-only CI artifacts, re-synced on every push.
• Kimi Code — the CLI edits ~/.kimi-code/config.toml at text level (a managed # >>> kimi-boost managed >>> block plus in-place array merge). Your comments and formatting survive untouched.
• Claude Code & Codex — manifest-driven install into ~/.claude / ~/.codex; agent files use the native frontmatter format (cross-compatible, per Kimi docs).
• Hooks are plain Node .mjs — the same pattern Kimi Code's own docs use, identical behavior on macOS / Windows / Linux.
• Compatibility is tested, not assumed — CI live-installs all 19 presets into a real Kimi Code CLI on every PR, and weekly against upstream drift.

• 🔒 Never touches your config beyond its own managed section — comments, ordering, formatting all preserved
• 🗄️ Backed up to <config>.kboost.bak before every change
• 🚧 Managed-roots whitelist — refuses to delete anything outside ~/.kimi-boost, ~/.kimi-code, ~/.claude, ~/.codex
• 🛡️ Dual-channel guard — already installed via Kimi /plugins? No duplicate hooks.
• ♻️ Content-aware hook dedup — presets bundling the same guard script (e.g. protect-main.mjs) share a single config entry; uninstalling one preset retargets the entry to the next owner instead of breaking the rest. doctor flags redundant or diverging hook copies.
• ⚡ Fail-open hooks — a crashing hook never blocks your work (exit 0 allow · exit 2 block)

• MCP server presets
• Token/cost usage guard hooks
• Official-channel distribution (single-plugin repo mirrors)
• Per-project (.kimi-boost/) presets
• More stack presets (vote in issue #1)
• Mirror every preset to its own official repo

Preset catalog is PR-driven: add a directory under presets/, CI validates schema, hook events and file existence — then live-installs your preset into a real Kimi Code CLI. See CONTRIBUTING.md.

MIT