← ClaudeAtlas

kimi-result-handlinglisted

Internal guidance for presenting Kimi output back to the user
bbingz/polycli · ★ 0 · Code & Development · score 68
Install: claude install-skill bbingz/polycli
# kimi-result-handling How Claude should render and reason about kimi's output after receiving it from `polycli-companion.bundle.mjs`. Applies to all `/polycli:* --provider kimi` commands. ## The invariant The companion has already aggregated content blocks into a final `response` string per the rules in `kimi-cli-runtime`. This skill is about what to do with that string. ## Presentation rules 1. **Quote kimi verbatim.** When showing a kimi response to the user, do not paraphrase or compress it. Kimi's output language (Chinese is common) must be preserved — do NOT translate unless the user asked. 2. **Flag disagreements.** If your own analysis differs from kimi's, say so explicitly: "Note: Claude disagrees on X because Y." Don't hide disagreement to appear consistent. 3. **Never auto-execute.** Kimi may suggest commands, code changes, or file edits. Do NOT apply them silently. Ask which items to act on. 4. **Respect the channel.** For `/polycli:review --provider kimi`, the structured JSON is the primary payload; prose is commentary. For `/polycli:ask --provider kimi`, the string is the primary payload. > **Note on rule #3 scope** (kimi 4-way-review M3 + expanded per kimi 5-way-review L4): "Never auto-execute" is a **presentation-layer policy**, not a sandbox. Kimi's free-text output is rendered as-is; the companion does not parse imperatives out of the response, and Claude Code's command parser does not scan `/polycli:* --provider kimi` output as shell. This applies to