Run any Skill in Manus with one click

kimi-setup

Stars21

Forks0

UpdatedJuly 11, 2026 at 20:39

Verify local Kimi companion readiness and manage the kimi-code PreToolUse hook plus optional review gate state. Use when explicitly requested to install, check, enable, disable, or uninstall the integration. Codex and Claude Code share one ~/.kimi-code/config.toml but each own a host-scoped block, so $kimi-setup here does not disturb Claude Code's /kimi:setup (and vice-versa).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

linxule

linxule/kimi-plugin-cc

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	kimi-setup
description	Verify local Kimi companion readiness and manage the kimi-code PreToolUse hook plus optional review gate state. Use when explicitly requested to install, check, enable, disable, or uninstall the integration. Codex and Claude Code share one ~/.kimi-code/config.toml but each own a host-scoped block, so $kimi-setup here does not disturb Claude Code's /kimi:setup (and vice-versa).

Kimi Setup

Forward this request to the local kimi-code companion runtime by shell. Do not use MCP for this skill.

Invocation

Resolve the plugin root: prefer $PLUGIN_ROOT if the host sets it; otherwise use the directory that CONTAINS the skills/ directory (i.e. two levels up from this SKILL.md).
Sanity check: <plugin-root>/scripts/companion.sh must exist — it is the bundled entrypoint that resolves Node and runs the compiled runtime from <plugin-root>/dist/.
Launch the shell command from the user's current workspace directory so scripts/companion.sh captures the intended workspace cwd.
Run: PLUGIN_ROOT="<plugin-root>" "<plugin-root>/scripts/companion.sh" setup <args>
If the plugin host provides PLUGIN_DATA instead of CLAUDE_PLUGIN_DATA, the shell wrapper exports the Claude-compatible alias for the runtime. If neither is set, the wrapper uses a Codex data directory under $CODEX_HOME/plugins/data/kimi-marketplace-kimi, ~/.codex/plugins/data/kimi-marketplace-kimi, or /tmp/kimi-plugin-cc-codex-data/kimi-marketplace-kimi in a fully sanitized environment.

Arguments

Pass through: [--check | --uninstall [--all] | --enable-review-gate | --disable-review-gate]

Handling

Run setup from the user's workspace so the companion records the intended workspace cwd.
Use --check for read-only verification and --uninstall only when explicitly requested. --uninstall removes only this host's block; --uninstall --all removes every host's block from the shared config.
Setup validates the complete shared TOML and every configured hook under a serialized lock. If it reports invalid foreign config, surface that failure; do not bypass it or claim the managed block is safe in isolation.
Report setup stdout verbatim because it contains hook and probe status.

More from this repository

same repository

kimi-ask

linxule/kimi-plugin-cc

Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.

2026-07-1121

kimi-challenge

linxule/kimi-plugin-cc

Run a read-only adversarial Kimi challenge review that questions assumptions, design choices, and tradeoffs. Use when the user wants pushback on whether the approach is right, not a defect-only review.

2026-07-1121

kimi-review

linxule/kimi-plugin-cc

Run an independent read-only Kimi review over the current working tree or a branch diff. Use when the user wants a second reviewer for defects, regressions, or implementation risks, not edits.

2026-07-1121

kimi-swarm

linxule/kimi-plugin-cc

Run a read-only parallel Kimi review fan-out across many independent targets. Use only for explicit broad fan-out requests where one subagent per target is the point.

2026-07-0521

kimi-swarm-write

linxule/kimi-plugin-cc

Run a write-capable Kimi swarm that edits many disjoint targets in a throwaway worktree and returns a reviewable patch. Use only for explicit parallel edit fan-out requests; the plugin never applies or commits the patch.

2026-07-0521

kimi-cancel

linxule/kimi-plugin-cc

Cancel an active plugin-managed Kimi job for the current repository. Use only when the user explicitly asks to cancel a Kimi run.

2026-06-2321

name	kimi-setup
description	Verify local Kimi companion readiness and manage the kimi-code PreToolUse hook plus optional review gate state. Use when explicitly requested to install, check, enable, disable, or uninstall the integration. Codex and Claude Code share one ~/.kimi-code/config.toml but each own a host-scoped block, so $kimi-setup here does not disturb Claude Code's /kimi:setup (and vice-versa).

Kimi Setup

Forward this request to the local kimi-code companion runtime by shell. Do not use MCP for this skill.

Invocation

Resolve the plugin root: prefer $PLUGIN_ROOT if the host sets it; otherwise use the directory that CONTAINS the skills/ directory (i.e. two levels up from this SKILL.md).
Sanity check: <plugin-root>/scripts/companion.sh must exist — it is the bundled entrypoint that resolves Node and runs the compiled runtime from <plugin-root>/dist/.
Launch the shell command from the user's current workspace directory so scripts/companion.sh captures the intended workspace cwd.
Run: PLUGIN_ROOT="<plugin-root>" "<plugin-root>/scripts/companion.sh" setup <args>
If the plugin host provides PLUGIN_DATA instead of CLAUDE_PLUGIN_DATA, the shell wrapper exports the Claude-compatible alias for the runtime. If neither is set, the wrapper uses a Codex data directory under $CODEX_HOME/plugins/data/kimi-marketplace-kimi, ~/.codex/plugins/data/kimi-marketplace-kimi, or /tmp/kimi-plugin-cc-codex-data/kimi-marketplace-kimi in a fully sanitized environment.

Arguments

Pass through: [--check | --uninstall [--all] | --enable-review-gate | --disable-review-gate]

Handling

Run setup from the user's workspace so the companion records the intended workspace cwd.
Use --check for read-only verification and --uninstall only when explicitly requested. --uninstall removes only this host's block; --uninstall --all removes every host's block from the shared config.
Setup validates the complete shared TOML and every configured hook under a serialized lock. If it reports invalid foreign config, surface that failure; do not bypass it or claim the managed block is safe in isolation.
Report setup stdout verbatim because it contains hook and probe status.