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

56%

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-keys/SKILL.md

Quality

Content

46%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 terse but flat command catalog: it enumerates subcommands and flags yet offers no real workflow, validation, or navigation, and repeats signatures as examples. Destructive operations lack the confirmation/validation checkpoints the rubric expects.

Suggestions

Replace the repeated-signature examples with concrete invocations using realistic arguments (e.g. 'omniroute keys rotate k_abc123 --grace-period 86400000 --yes') and add a short workflow showing key lifecycle: create -> use -> rotate -> revoke.

Add validation/confirmation guidance for destructive and batch operations (revoke, remove, rotate), such as running 'keys show <id>' or 'keys list' to verify before/after.

Remove the duplicate 'keys list' section and either consolidate flag references or move the full command reference into a separate file linked from a concise overview.

Dimension	Reasoning	Score
Conciseness	It is mostly a compact command catalog with little padding, but the Overview duplicates the description verbatim and every subcommand repeats its own signature as an 'Example', adding redundant tokens that could be trimmed.	3 / 5
Actionability	Commands and flags are listed, but examples are just the bare command signature repeated rather than copy-paste ready invocations with real arguments, and there are no concrete sample values for flags like --rate-limit or --allowed-models.	3 / 5
Workflow Clarity	There is no multi-step workflow or sequencing; destructive/batch operations (revoke, remove, rotate) lack validation or confirmation guidance, and the rubric caps workflow clarity at 3 for such operations, with the absence of any checkpoint pushing it lower.	2 / 5
Progressive Disclosure	Subcommand sections give some structure, but the body is a flat monolithic command listing with no external references or one-level-deep navigation; a duplicated 'keys list' section also signals weak organization.	3 / 5
	Total	11 / 20 Passed

Description

66%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 with a distinct OmniRoute niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding a usage trigger would lift the weakest dimension.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user needs to manage OmniRoute API keys or set up provider OAuth authentication.'

Add common natural trigger terms and synonyms such as 'rotate keys', 'revoke tokens', and 'key scopes'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create, list, rotate, and revoke OmniRoute API keys' plus 'Manage OAuth flows' and 'inspect key scopes and expiration' — covering the skill comprehensively.	5 / 5
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural user-facing terms like 'API keys', 'OAuth flows', and 'scopes and expiration', but omits common synonyms and file/CLI invocations a user might actually say (e.g. 'rotate keys', 'revoke a token').	4 / 5
Distinctiveness Conflict Risk	The 'OmniRoute API keys' and 'OAuth flows' niche is fairly distinct with clear triggers; only minor overlap risk with a generic key/secret management skill.	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-keys/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.