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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

61%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 well-structured, actionable CLI command reference with clear external links, but it is padded by a redundant auto-generated stub section and lacks validation checkpoints around its destructive/batch key and combo operations.

Suggestions

Remove or collapse the auto-generated stub section (empty descriptions, '[subcommand]' placeholders, the truncated '(use ' line) to eliminate duplication with the curated section.

Add explicit validation/verification steps for destructive and batch operations (e.g. run 'providers test' after 'keys rotate', or 'providers list' after 'keys remove'/'combo delete').

Dimension	Reasoning	Score
Conciseness	The curated section is lean, but the auto-generated stub section duplicates it and includes broken/placeholder content ('Manage provider connections (use ' and literal '[subcommand]' examples), adding unnecessary tokens.	3 / 5
Actionability	Provides many concrete, executable commands with real flags plus a useful errors/troubleshooting section; placeholder stubs in the auto-generated portion keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	Content is a categorized command catalog rather than a sequenced workflow, and destructive/batch operations (keys remove, keys revoke, combo delete, test-all) lack validation checkpoints, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clear sections with two clearly signaled one-level external references (CLI entry-point and routing skills); the inlined command catalog is appropriate for a CLI reference, with only minor organization gaps from the duplicated auto-generated section.	4 / 5
	Total	14 / 20 Passed

Description

71%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 action-rich, clearly scoping a distinct CLI niche, but it omits any explicit 'Use when' trigger guidance, which limits completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when managing provider connections, rotating API keys, or checking provider metrics from the CLI').

Add natural synonyms or extensions users might say (e.g. 'API keys', 'credentials', 'connections') to broaden trigger coverage.

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' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is clearly stated but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('providers', 'API keys', 'rotate', 'test', 'validate', 'metrics') but lacks synonyms or extensions; good coverage with a few common variations missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (CLI provider-connection management) that is mostly distinct from sibling skills, with only minor overlap risk; no explicit trigger phrase keeps it just below 5.	4 / 5
	Total	16 / 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-providers/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.