qiaomu-model-cli

Route tasks to local Grok, Kimi, and Claude CLIs with concurrent batch execution and artifact verification.

43|8|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/joeseesun/qiaomu-model-cli --skill qiaomu-model-cli-joeseesun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qiaomu-model-cli
Source: https://github.com/joeseesun/qiaomu-model-cli
Command: npx skills add https://github.com/joeseesun/qiaomu-model-cli --skill qiaomu-model-cli-joeseesun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Orchestrating multiple local AI model CLIs (Grok, Kimi Code, Claude Code) by hand means writing raw CLI flags, waiting on serial calls, and trusting exit codes that do not prove files were actually produced. This Skill routes each task to the right CLI with strong default models, runs independent jobs concurrently, verifies artifacts, and retries only failed jobs. ## Core Features & Use Cases - Model Routing: Sends X/web search, image, and video tasks to Grok CLI (grok-4.5), frontend UI work to Kimi Code CLI (kimi-code/k3, 1M context), and complex coding or review to Claude Code CLI (Fable 5 default, Opus 4.8 / Sonnet 5 optional). - Concurrent Batch with Done Gate: Launches independent jobs in one batch call with isolated working directories, native JSON stream progress events, private per-job logs, and expects/verify_commands artifact checks so a zero exit code alone never counts as success. - Retry and Cancellation: Ctrl-C terminates all active process groups, and retry --summary reruns only failed jobs from a prior run without repeating successful ones. - Use Case: Ask three models to each build a landing page version; the Skill creates one batch config, starts Grok, Kimi, and Claude concurrently in separate directories, verifies each index.html exists, and reports a side-by-side summary. ## Quick Start Ask the agent to use qiaomu-model-cli to run a task, for example: use grok cli to search the latest posts from an X account, or run a batch comparing Grok 4.5, Kimi K3, and Claude Opus 4.8 on the same page-building task.

Frequently Asked Questions about qiaomu-model-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Grok, Kimi, and Claude CLIs concurrently for the same task?▼

Create a batch JSON config with one job per provider, each using its own isolated cwd, then invoke the wrapper once with batch --config and --max-workers set to at least the job count. All providers start together and results land in a shared summary.json.

Which model should I use for frontend UI work, Kimi K3 or Claude?▼

Kimi Code CLI with kimi-code/k3 (1M context) is the default for frontend UI, CSS, React, and Vue implementation. Claude Code with Fable 5 is reserved for the most complex coding and refactoring, while Sonnet 5 suits faster everyday frontend fixes.

How do I verify that a model CLI actually produced the expected files?▼

Declare expects entries with paths and min_bytes, plus argv-based verify_commands such as a build command, in the job or batch defaults. A provider that exits successfully but fails these checks returns code 3 instead of being marked done.

Can I retry only the failed jobs from a previous batch run?▼

Yes, run retry --summary pointing at the prior run's summary.json. It loads the private run-config.json, selects only jobs where ok is false, and executes them in a fresh run directory without rerunning successful jobs.

Why does Kimi CLI fail when combining --prompt with --yolo or --auto?▼

The current Kimi Code CLI does not allow -p/--prompt together with --yolo or --auto. Use pure non-interactive -p mode from agents and avoid stacking those flags.

What are the prerequisites for using local Grok, Kimi, and Claude CLIs?▼

Each CLI binary must be installed and on PATH, authenticated via grok login, kimi login, or claude auth, and Python 3.10+ is required. Run scripts/check_env.py to verify binaries, login state, and default model availability before invoking tasks.