Skip to content

/kimi-ask

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.

From plugin
2912 skills7 agents12 commands1 hooks
shell
$ npx -y skills add linxule/kimi-plugin-cc --skill kimi-ask --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/kimi-ask
How auto-invocation works

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

kimi-ask.SKILL.md
name: kimi-ask
description: "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."

Kimi Ask

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" ask <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: `[--background] [--wait] [-r | --resume <id>] [--fresh] [-m <model>] <prompt>`

Handling

  • Preserve the user's question and supplied flags exactly; use `-r` only for explicit resume intent unless `--fresh` is requested.
  • Choose `--background` for broad or long-running questions and return the job id that the companion prints.
  • If the companion reports ASK_HOOK_NOT_INSTALLED, tell the user to run Claude Code /kimi:setup or Codex $kimi-setup, then retry; do not suggest the skip env.
  • Return companion stdout verbatim; do not summarize or re-voice Kimi's prose.
Read more
Read it on GitHub ↗
Ships withkimi

Use Kimi as Claude Code's second reviewer, independent thinker, and delegated worker — without building your own multi-agent stack. This is a Claude Code plugin that drives the kimi-code CLI (the Node.js successor to Kimi CLI) as a subprocess.

Get the whole plugin, auto-invoked
Stats
29
Stars
0
Views
1
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
2d ago
Last commit
3mo ago
Created

Repo: linxule/kimi-plugin-cc