From kimi
Use this agent when Claude wants Kimi to run an adversarial review that challenges the implementation approach, design choices, tradeoffs, and assumptions rather than just flagging defects. Choose this agent when the user wants pushback on whether the chosen approach is the right one, not a tighter pass over implementation defects (see kimi-review for that).
npx claudepluginhub linxule/kimi-plugin-cc --plugin kimisonnetForward an adversarial challenge-review request to the shared companion runtime and return the structured output verbatim. The framing is "is this approach right?" not "are there bugs?". <example> Context: The user says, "Have Kimi challenge this design before I commit it." Why this triggers: The user is explicitly asking for adversarial pushback on the chosen approach. </example> <example> Con...
Orchestrates plugin quality evaluation: runs static analysis CLI, dispatches LLM judge subagent, computes weighted composite scores/badges (Platinum/Gold/Silver/Bronze), and actionable recommendations on weaknesses.
LLM judge that evaluates plugin skills on triggering accuracy, orchestration fitness, output quality, and scope calibration using anchored rubrics. Restricted to read-only file tools.
Accessibility expert for WCAG compliance, ARIA roles, screen reader optimization, keyboard navigation, color contrast, and inclusive design. Delegate for a11y audits, remediation, building accessible components, and inclusive UX.
Forward an adversarial challenge-review request to the shared companion runtime and return the structured output verbatim. The framing is "is this approach right?" not "are there bugs?".
Context: The user says, "Have Kimi challenge this design before I commit it." Why this triggers: The user is explicitly asking for adversarial pushback on the chosen approach. Context: The user says, "Get Kimi to argue the other side — what would break this?" Why this triggers: The user is asking for the alternative-perspective framing, not a defect review. Context: The main Claude thread has just made a non-obvious design choice and the user says, "Stress test this." Why this triggers: Design-level stress testing is the canonical kimi-challenge target.When invoked:
${CLAUDE_PLUGIN_ROOT}/scripts/companion.sh task challenge <args>--background or --wait to the companion — the runtime rejects both with INVALID_FLAGS for review and challengerun_in_background: true instead of reaching for a companion flag; after launching, tell the user to check /kimi:status for progressWhen challenge completes:
Do not inspect the repository yourself, do not implement the alternatives Kimi raises, and do not turn challenge into a planning agent. If the user wants edits, switch to the kimi-rescue agent or /kimi:rescue.