Auto-invoked
/kimi-status
Show the latest or selected plugin-managed Kimi job for the current repository. Use when the user explicitly asks for Kimi job status or progress.
Claude Code
$ npx -y skills add linxule/kimi-plugin-cc --skill kimi-status --agent claude-code
Codex
$ npx skills add linxule/kimi-plugin-cc --skill kimi-status -a codex -y
Cursor
$ npx skills add linxule/kimi-plugin-cc --skill kimi-status -a cursor -y
Gemini CLI
$ npx skills add linxule/kimi-plugin-cc --skill kimi-status -a gemini-cli -y
GitHub Copilot
$ npx skills add linxule/kimi-plugin-cc --skill kimi-status -a github-copilot -y
OpenCode
$ npx skills add linxule/kimi-plugin-cc --skill kimi-status -a opencode -y
Windsurf
$ npx skills add linxule/kimi-plugin-cc --skill kimi-status -a windsurf -y
SKILL.md
kimi-status.SKILL.mdname: kimi-status
description: "Show the latest or selected plugin-managed Kimi job for the current repository. Use when the user explicitly asks for Kimi job status or progress."
Kimi Status
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" status <args>`
- Data directories: standard cache installs verify shared `CLAUDE_PLUGIN_DATA`/`PLUGIN_DATA` against this package's own host-specific directory. On `PLUGIN_DATA_CONFLICT`, surface the error; do not automatically choose a new store or copy data. An explicit absolute `KIMI_PLUGIN_CC_DATA` selects a custom data parent (the runtime appends `kimi-plugin-cc/`). Checkouts retain unambiguous legacy variables and the Codex fallback under `CODEX_HOME` or `HOME`; a launch with no home needs an explicit data root.
Arguments
Pass through: `[<job-id>] [--type <review|challenge|rescue|review_gate|ask>]`
Handling
- Preserve any job id or `--type` filter.
- Return companion stdout verbatim; it is the persisted job state.
Read more
name: kimi-status description: "Show the latest or selected plugin-managed Kimi job for the current repository. Use when the user explicitly asks for Kimi job status or progress."
Kimi Status
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" status <args>`
- Data directories: standard cache installs verify shared `CLAUDE_PLUGIN_DATA`/`PLUGIN_DATA` against this package's own host-specific directory. On `PLUGIN_DATA_CONFLICT`, surface the error; do not automatically choose a new store or copy data. An explicit absolute `KIMI_PLUGIN_CC_DATA` selects a custom data parent (the runtime appends `kimi-plugin-cc/`). Checkouts retain unambiguous legacy variables and the Codex fallback under `CODEX_HOME` or `HOME`; a launch with no home needs an explicit data root.
Arguments
Pass through: `[<job-id>] [--type <review|challenge|rescue|review_gate|ask>]`
Handling
- Preserve any job id or `--type` filter.
- Return companion stdout verbatim; it is the persisted job state.
Stats
43
Stars
3
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
Last commit
Created
Ships withkimi
Use Kimi to explain code, review changes, challenge a design, or work toward a goal — an independent second opinion from a different model family, inside the Claude Code, Codex, or DeepSeek Harness session you're already in. I'm a Kimi Ambassador (academia).
4312 skills7 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 43
Other skills on kimi.
Auto-invoked
Auto-invoked
Auto-invoked
Auto-invoked
Auto-invoked
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about kimi-status.
- Which coding agents can use kimi-status?
- kimi-status installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.