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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

65%

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

The skill body is a concise, auto-generated CLI reference that is token-efficient and well-structured. It is weakened by examples that omit flag values and by the absence of validation/verification guidance for batch operations.

Suggestions

Show at least one complete example per subcommand with real flag values (e.g. `omniroute batches create --endpoint X --completion-window 24h --metadata job=test`).

Add verification guidance for batch workflows — e.g. run `batches get`/`batches errors` after `submit`/`wait` to confirm success before proceeding.

Consider linking to an external reference (e.g. API reference or examples file) to split the subcommand catalog out of the overview.

Dimension	Reasoning	Score
Conciseness	The body is a lean, templated CLI reference with no conceptual padding; it assumes Claude's competence and every command/flag earns its place.	3 / 3
Actionability	Commands are concrete and copy-pasteable, but examples omit flag values (e.g. `omniroute batches create` and `omniroute batches submit` show no arguments), leaving guidance incomplete per the 'missing key details' anchor.	2 / 3
Workflow Clarity	Subcommands are listed in a clear sequence, but batch operations (create/submit/wait/output/errors) lack validation or verification checkpoints, which caps workflow_clarity at 2 per the feedback-loop scoring note.	2 / 3
Progressive Disclosure	Sections are well organized and no external bundle files exist, but there are no one-level-deep references or navigation pointers to detail; structure is present but could be better signaled for an API surface this size.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 is specific and distinctive, clearly conveying concrete batch-CLI capabilities in third person. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term coverage slightly thin.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to run, submit, or monitor batch inference jobs from the CLI'.

Broaden trigger terms to include natural variations users would say, such as 'batch jobs', 'batch API', or 'batch results'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Submit and monitor batch inference jobs', 'Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows' — matching the multi-action anchor.	3 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains relevant terms ('batch inference', 'batch processing', 'CI/CD') but lacks common natural variations a user would say ('batch jobs', 'batch API'); missing some keyword coverage per the anchor.	2 / 3
Distinctiveness Conflict Risk	Has a clear niche — CLI batch inference job management — with distinct triggers unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 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: 3070925

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.