cli-resilience

Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.

Quality

70%

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

Fix and improve this skill with Tessl

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

Quality

Content

65%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.

A terse, mostly executable CLI reference, undermined by duplicated `resilience show`/`set` sections (with inconsistent flags), a verbatim-repeated overview, examples that omit flag usage, and no validation guidance for the destructive reset command.

Suggestions

De-duplicate the `resilience show` and `resilience set` sections, merging the stray flags (`--threshold`, `--reset-timeout`, `--base-cooldown`) into a single `set` entry.

Add a validation/verification note to `resilience reset` (e.g., run `resilience status`/`breakers` after to confirm) so the destructive operation clears the workflow_clarity cap.

Show flag usage in at least one example per subcommand (e.g., `omniroute resilience reset --all-cooldowns --yes`) and drop the redundant Overview that repeats the description.

Dimension	Reasoning	Score
Conciseness	Lean command reference that assumes Claude's competence and avoids concept over-explanation, but the Overview duplicates the description verbatim and the duplicated `resilience show`/`set` sections waste tokens, keeping it off the 5 anchor.	4 / 5
Actionability	Provides concrete, executable `omniroute` commands with flags listed per subcommand; not 5 because examples are bare invocations that never demonstrate flag usage in context, leaving a minor gap.	4 / 5
Workflow Clarity	Content is a flat command reference with no sequenced workflow, and the destructive `resilience reset` (with `--all-cooldowns`/`--yes`) carries no validation or verification guidance, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Reasonable per-subcommand section headers but everything is inlined in a >50-line file with no external references and duplicated `show`/`set` sections, matching the "some structure but could be better organized" 3 anchor rather than 4.	3 / 5
	Total	14 / 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.

A specific, third-person description with strong action coverage and a clear niche, but it omits any explicit "when to use" trigger guidance, which caps completeness.

Suggestions

Add a "Use when…" clause (e.g., "Use when a provider is stuck in cooldown or a circuit breaker won't close") to lift completeness above 3.

Include a couple of natural synonyms or phrasings a user might say (e.g., "provider down", "rate limited") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Inspect and manage", "Reset", "configure") applied to specific objects (circuit-breaker states, connection cooldowns, quota limits, backoff levels, resilience thresholds), giving comprehensive coverage; not the 4 anchor because no meaningful action gaps remain.	5 / 5
Completeness	Has a clear "what" but no "Use when…" clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3; it does not reach 4 which requires an explicit "when".	3 / 5
Trigger Term Quality	Good domain keyword coverage ("circuit-breaker", "cooldowns", "quota limits", "backoff", "providers", "resilience thresholds") that a user of this tool would naturally say; not 5 because it lacks common synonyms or a file/extension-style trigger and is somewhat jargon-bound.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (CLI resilience/circuit-breaker management) with distinct triggers unlikely to fire for unrelated skills; minimal conflict risk, matching the 5 anchor.	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-resilience/SKILL.md
Commit: ea0cdc5

Reviewed: 3 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.