メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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).
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.
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.
Cancel an active plugin-managed Kimi job for the current repository. Use only when the user explicitly asks to cancel a Kimi run.
| name | kimi-challenge |
| description | 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. |
Forward this request to the local kimi-code companion runtime by shell. Do not use MCP for this skill.
$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).<plugin-root>/scripts/companion.sh must exist — it is the bundled entrypoint that resolves Node and runs the compiled runtime from <plugin-root>/dist/.scripts/companion.sh captures the intended workspace cwd.PLUGIN_ROOT="<plugin-root>" "<plugin-root>/scripts/companion.sh" task challenge <args>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.Pass through: [--base <ref>] [-m <model>] [extra prose]