cli-keys

Create, list, rotate, and revoke OmniRoute API keys from the CLI. Manage OAuth flows for provider authentication and inspect key scopes and expiration.

Quality

66%

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-keys/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 CLI command/flag reference with good token efficiency, but it stops short of executable examples and lacks validation workflows for its destructive key operations. Structure is flat rather than progressively disclosed.

Suggestions

Show at least one fully executable example per destructive subcommand (e.g., "omniroute keys revoke abc123 --yes") instead of bare placeholder templates.

Add a brief validation/confirmation step or note for remove/revoke/regenerate/rotate (e.g., run "keys show <id>" or "keys list" afterward to confirm the change took effect).

Add a short overview that signals which subcommands are read-only vs. mutating, so Claude can navigate the reference rather than scanning every entry.

Dimension	Reasoning	Score
Conciseness	The body is lean with no conceptual padding or over-explanation of things Claude already knows; each section is a terse command/flag listing that earns its tokens.	3 / 3
Actionability	Commands and flags are concrete, but the examples are non-executable templates ("<provider>", "<id>") and flag-value usage like "--allowed-models <list>" is never shown with real values, leaving guidance incomplete.	2 / 3
Workflow Clarity	Subcommands are listed but destructive operations (keys remove/revoke/regenerate/rotate) rely on a bare "--yes" flag with no confirm-validate sequence or checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	It is a single flat reference listing with clear subcommand sections, but there is no overview-to-detail navigation and no bundle references to split out deeper material, so structure is only adequate.	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 distinct, naming concrete CLI actions for OmniRoute key and OAuth management. Its main weakness is the missing "Use when..." trigger clause and slightly jargon-forward terminology.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g., when the user wants to manage or rotate OmniRoute API keys, set up OAuth provider connections, or check key scopes/expiration).

Soften jargon with natural phrasings users would actually say, such as "API keys", "login connections", or "permissions" alongside "OAuth" and "scopes".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Create, list, rotate, and revoke") plus OAuth flow management and scope/expiration inspection, matching the multi-action anchor.	3 / 3
Completeness	Clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Relevant terms like "API keys", "OAuth", "scopes", and "expiration" appear, but they skew technical and omit common natural phrasings a user would actually say.	2 / 3
Distinctiveness Conflict Risk	The OmniRoute CLI API-key/OAuth niche is specific with distinct triggers, making it unlikely to fire for 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-keys/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.