cli-batches — Claude Code skill: what it does, how to install
Submit and monitor batch inference jobs from the CLI using OmniRoute. Upload input files, inspect batch status, and retrieve results for CI/CD pipelines.
npx skills add cheaper-inference/OmniRoute --skill cli-batches -a claude-codeWhat cli-batches does
This skill provides commands to run batch inference through the omniroute CLI. With omniroute batches submit, you pass a JSONL file, choose an endpoint, and optionally hold execution using --wait. Tasks can also be staged separately by uploading files and passing IDs to batches create.
File handling relies on the omniroute files subcommand. It covers file uploads, content retrieval, and deletions with confirmation flags. If execution fails, errors can be exported to a separate file using omniroute batches errors.
Working with this skill requires the omniroute binary installed globally via npm or executed with npx. Without the underlying CLI tool available in your path, every command will fail.
What it helps with
- submit JSONL files for batch model inference
- monitor batch job execution and retrieve output files
- upload and manage remote files for processing
- inspect error logs from failed batch runs
Example prompts for the agent
- Submit data.jsonl for batch processing with omniroute batches submit
- Check the progress of batch <batchId> using omniroute batches wait
- Save batch errors for <batchId> to an output file via omniroute batches errors
How to install cli-batches
1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-batches -a claude-code2Manually: put the files in place
~/.claude/skills/cli-batches/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cli-batches/
1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-batches -a codex2Manually: put the files in place
.agents/skills/cli-batches/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-batches -a cursor2Manually: put the files in place
.cursor/skills/cli-batches/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cheaper-inference/OmniRoute cli-batches2Manually: put the files in place
.github/skills/cli-batches/SKILL.md1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-batches -a gemini-cli2Platform CLI
gemini skills install https://github.com/cheaper-inference/OmniRoute --path skills/cli-batchesManually: put the files in place
.devin/skills/cli-batches/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-batches -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set34
The whole set →Similar
Questions about cli-batches
How to install cli-batches in Claude Code?
Run npx skills add cheaper-inference/OmniRoute --skill cli-batches -a claude-code in your terminal. You must also install the CLI tool via npm install -g omniroute.
What does the cli-batches skill do?
It lets you submit batch inference workloads, monitor their status, and manage processing files directly from the command line.
What prerequisites are needed for cli-batches?
You need Node.js with omniroute installed globally via npm or run through npx. Check the tool with omniroute --version.
Source text
SKILL.md · MIT
--- name: cli-batches description: Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows. --- <!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten --> ## Overview Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows. ## Quick install ```bash npm install -g omniroute # or: npx omniroute omniroute --version ``` ## Subcommands ### `batches` **Example:** ```bash omniroute batches ``` ### `batches list` **Flags:** - `--status <s>` - `--limit <n>` **Example:** ```bash omniroute batches list ``` ### `batches get <batchId>` **Example:** ```bash omniroute batches get <batchId> ``` ### `batches create` **Flags:** - `--input-file <fileId>` - `--endpoint <e>` - `--completion-window <w>` - `--metadata <kv>` **Example:** ```bash omniroute batches create ``` ### `batches submit` **Flags:** - `--jsonl <path>` - `--endpoint <e>` - `--wait` **Example:** ```bash omniroute batches submit ``` ### `batches cancel <batchId>` **Flags:** - `--yes` **Example:** ```bash omniroute batches cancel <batchId> ``` ### `batches wait <batchId>` **Flags:** - `--timeout <ms>` **Example:** ```bash omniroute batches wait <batchId> ``` ### `batches output <batchId>` **Flags:** - `--out <path>` **Example:** ```bash omniroute batches output <batchId> ``` ### `batches errors <batchId>` **Flags:** - `--out <path>` **Example:** ```bash omniroute batches errors <batchId> ``` ### `files` **Example:** ```bash omniroute files ``` ### `files list` **Flags:** - `--purpose <p>` - `--limit <n>` **Example:** ```bash omniroute files list ``` ### `files get <fileId>` **Example:** ```bash omniroute files get <fileId> ``` ### `files upload <path>` **Flags:** - `--purpose <p>` **Example:** ```bash omniroute files upload <path> ``` ### `files content <fileId>` **Flags:** - `--out <path>` **Example:** ```bash omniroute files content <fileId> ``` ### `files delete <fileId>` **Flags:** - `--yes` **Example:** ```bash omniroute files delete <fileId> ```
© cheaper-inference · MIT · cheaper-inference/OmniRoute