Cli Batches
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.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Cli Batches when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Cli Batches when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/cli-batches # Save SKILL.md to ~/.claude/skills/cli-batches/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-batches/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-batches/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Cli Batches skill for this task: Use Cli Batches when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- 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> ```
Intended uses
- Use Cli Batches when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.