minimax-result-handlinglisted

# minimax-result-handling How Claude should render and reason about MiniMax output after receiving it from `polycli-companion.bundle.mjs`. Applies to all `/polycli:* --provider minimax` commands. ## The invariant The companion has already: 1. Spawned `mmx text chat --message <prompt> --output json --non-interactive` 2. Parsed the JSON response directly 3. Classified empty output, auth failures, and CLI failures into the shared Polycli result shape This skill is about what to do with the final text/JSON payload that companion wrote to stdout (or the error on stderr). ## Presentation rules 1. **Quote MiniMax verbatim.** When showing the response to the user, do not paraphrase or compress. MiniMax M2 often replies in Chinese when the prompt is Chinese; do NOT translate unless the user explicitly asked. 2. **Flag disagreements.** If your own analysis differs, say so explicitly: "Note: Claude disagrees on X because Y." Don't hide disagreement to appear consistent. 3. **Never auto-execute.** MiniMax 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 minimax` (Phase 3) the structured JSON is the primary payload; prose is commentary. For `/polycli:ask --provider minimax`, the response string is the primary payload. 5. **Do NOT explain the cold start.** The companion already printed a `Starting MiniMax (cold start ~3s)...` line. Do not add your own "MiniMax is slow