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.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-batches/SKILL.md

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, well-structured CLI command catalogue that respects token budget and navigation, but it lacks example flag values, a sequenced batch workflow, and the validation/verification steps the rubric requires for batch and destructive operations.

Suggestions

Show realistic flag values in examples (e.g. `omniroute batches create --endpoint chat --completion-window 24h`) instead of bare placeholders like `<e>` and `<kv>`.

Add a short end-to-end workflow showing the create -> submit -> wait -> output sequence so Claude knows the intended order of operations.

Add verification/checkpoint guidance for destructive commands (e.g. confirm batch status with `batches get` before `cancel`, and `--yes` only after a confirmation prompt) to lift the workflow-clarity cap.

Dimension	Reasoning	Score
Conciseness	The body is largely a compact command/flag catalogue with no padding or explanation of concepts Claude already knows; the only redundancy is the Overview repeating the frontmatter description verbatim, which is minor over-explanation.	4 / 5
Actionability	Each subcommand shows an executable `omniroute ...` invocation and lists flags, but flags use placeholder tokens like `<e>`, `<w>`, `<kv>` with no example values, and `batches create`/`batches submit` examples omit the required flags entirely, leaving key execution details missing.	3 / 5
Workflow Clarity	Commands are enumerated per subcommand but there is no end-to-end batch workflow (create -> submit -> wait -> output) and, critically for a batch skill, no validation or verification steps before destructive operations like `cancel`/`delete`, so workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md under 50 lines per subcommand with clear section headers and no external references needed, satisfying the simple-skill exception for progressive disclosure at 5.	5 / 5
	Total	15 / 20 Passed

Description

51%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a clear domain and several concrete actions, but it omits any explicit 'Use when...' trigger guidance and relies on fairly generic file-management phrasing, limiting trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when submitting batch inference jobs, polling batch status, or wiring batch runs into CI/CD').

Include synonyms and concrete file extensions users would say, such as '.jsonl batch input files' and 'batch API', to improve trigger-term coverage.

Tighten the file-management wording to batch-specific terms ('upload batch input files') to reduce overlap with generic file skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Submit and monitor batch inference jobs', 'Upload and manage files', 'retrieve results', 'integrate batch pipelines with CI/CD'), but each action is stated only at a high level without sub-capabilities, leaving minor gaps in coverage.	4 / 5
Completeness	It clearly states what the skill does but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Domain terms are present ('batch inference jobs', 'batch processing', 'CI/CD workflows') but it lacks the natural phrases a user would actually say ('batch API', 'batch jobs', '.jsonl', 'upload file for batch') and offers no synonyms or file-extension triggers.	2 / 5
Distinctiveness Conflict Risk	'Submit and monitor batch inference jobs from the CLI' carves a recognizable niche, yet 'upload and manage files' and 'retrieve results' are generic enough that the description could overlap with general file-management skills.	3 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: diegosouzapw/OmniRoute
Path: skills/cli-batches/SKILL.md
Commit: ea0cdc5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.