cli-providers

Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-providers/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 body is highly actionable with concrete executable commands, but carries redundant auto-generated content, lacks validation checkpoints for destructive key operations, and keeps everything in one monolithic file with only remote references.

Suggestions

Remove or collapse the auto-generated top section that duplicates the curated subcommand reference to cut redundancy.

Add explicit validation/safety steps for destructive operations (e.g. run 'providers test' after 'rotate', confirm before 'keys revoke').

Move keys, combos, and nodes sections into local reference files under references/ and link to them to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-reference format, but the auto-generated top section duplicates subcommands re-covered by the curated section and many Example blocks repeat the heading command verbatim with no added value, so it is not fully lean.	2 / 3
Actionability	Concrete, copy-paste-ready commands with flags and inline comments throughout (e.g. 'omniroute keys policy set <id> --rate-limit 100 --rate-window minute --permissions chat,models'), matching the fully executable anchor.	3 / 3
Workflow Clarity	Sequencing/validation is implicit and the Errors section gives troubleshooting, but destructive/batch operations like 'rotate' and 'keys revoke' lack validation checkpoints, which the guidelines cap at 2.	2 / 3
Progressive Disclosure	Sections are clearly headed and external links are one-level-deep, but no bundle files exist, the links point to remote raw GitHub URLs, and keys/combos/nodes content that could be split out is inlined into one monolithic file.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 action-rich with natural trigger terms, but it omits any explicit 'Use when...' guidance, capping completeness, and its niche overlaps with adjacent omniroute skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs to manage provider connections, test or rotate API keys, or check provider metrics from the CLI.'

Sharpen distinctiveness by scoping to OmniRoute specifically and contrasting with the routing/cli skills it could be confused with.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is explicit but there is no 'Use when...' clause or equivalent trigger guidance, which the guidelines cap at 2; not level 3 because the 'when' is entirely missing.	2 / 3
Trigger Term Quality	Natural terms a user would say ('providers', 'API keys', 'rotate API keys', 'metrics') are present with good coverage, fitting the 'good coverage of natural terms' anchor rather than the jargon-only level 1.	3 / 3
Distinctiveness Conflict Risk	'Manage provider connections from the CLI' is a defined niche but overlaps with sibling omniroute-cli / omniroute-routing skills, so it could still trigger for the wrong skill rather than having a fully distinct niche.	2 / 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-providers/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.