cli-models

Query available AI models, list model aliases, and browse the full model catalog from the CLI. Filter by provider, search by capability, and resolve model name variants.

Quality

80%

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

Quality

Content

86%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 body is a clean, token-efficient CLI reference with well-organized sections and executable commands. It could be improved by richer examples showing flag usage and by documenting the alias/variant-resolution actions mentioned in the description.

Suggestions

Replace the placeholder example `omniroute models [provider]` with a real invocation using flags and expected output, e.g. `omniroute models openai --search vision --json`.

Document the actions the description promises but the body omits — listing aliases and resolving model name variants — as concrete subcommands or flag examples.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or over-explanation — install command, version check, subcommand signature, flags, and a single example — every token earns its place and Claude's competence is assumed.	5 / 5
Actionability	Provides concrete executable commands (`npm install -g omniroute`, `omniroute models [provider]`) and flags (`--search`, `--json`), but the example merely restates the heading without showing flag usage or sample output, leaving a minor gap.	4 / 5
Workflow Clarity	For this simple single-purpose CLI skill the install-then-run sequence is clear and unambiguous, but only the `models` subcommand is shown while the description references alias listing and variant resolution that are not demonstrated.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed; content is well-organized into Overview, Quick install, and Subcommands sections, meeting the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

75%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 is specific and distinct, naming multiple concrete CLI actions around model querying, aliasing, and filtering. Its main weakness is the absence of any explicit 'Use when...' trigger guidance, which limits completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when listing available AI models, resolving model name aliases, or filtering models by provider/capability from the CLI.'

Include a few more natural user phrases like 'available models' or 'which models are supported' to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists six concrete actions — 'Query available AI models', 'list model aliases', 'browse the full model catalog', 'Filter by provider', 'search by capability', 'resolve model name variants' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	It clearly answers 'what' with multiple concrete actions, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('AI models', 'model aliases', 'model catalog', 'provider', 'capability'), but a few common variations a user might say (e.g. 'available models', 'which models') are missing.	4 / 5
Distinctiveness Conflict Risk	The CLI model-catalog niche (querying models, aliases, provider filtering) is distinct with specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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-models/SKILL.md
Commit: 6435f61

Reviewed: about 19 hours 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.