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

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

50%

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 concise CLI command reference, but it suffers from duplicated sections, missing flags on several subcommands, and no workflow/validation guidance for the destructive reset operation. Tightening duplicates and adding flag-bearing examples would improve it.

Suggestions

Remove the duplicated 'resilience show' and 'resilience set' sections, merging flags into a single entry per subcommand.

Add the flags each subcommand accepts into its example command (e.g., 'omniroute resilience reset --connection-id <id> --yes') and list flags for the subcommands currently missing them.

Add a brief validation/confirmation step around 'resilience reset' (e.g., inspect status before, confirm with --yes) since it performs destructive batch changes.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command reference, but the Overview repeats the frontmatter description verbatim and the 'resilience show' and 'resilience set' sections are duplicated, wasting tokens; matching the score-2 'could be tightened' anchor.	2 / 3
Actionability	Concrete commands like 'omniroute resilience status' are present, but examples omit flag usage and several subcommands (resilience, profile, show, set, config) list no flags, leaving guidance incomplete — matching the score-2 anchor.	2 / 3
Workflow Clarity	Commands are listed as discrete steps but there is no sequencing guidance and no validation checkpoint for the destructive 'resilience reset' (with --all-cooldowns/--yes), so per the guidelines workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	Content is organized into named subcommand sections with no external references needed, but the duplicated show/set sections and flat over-50-line listing reflect structure that could be better organized, matching the score-2 anchor.	2 / 3
	Total	8 / 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 occupies a clear niche, but it omits explicit 'when to use' trigger guidance and could include more natural user phrasings. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming the natural situations that should trigger this skill (e.g., when a provider is stuck, when circuit breakers or cooldowns need inspection or reset).

Include more conversational trigger terms users would actually say, such as 'provider is stuck', 'reset breaker', or 'check quota', alongside the technical jargon.

Dimension	Reasoning	Score
Specificity	Quotes 'Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels... Reset stuck providers and configure resilience thresholds' — a list of multiple concrete actions, matching the score-3 anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like 'circuit-breaker states', 'cooldowns', 'quota limits', 'backoff levels' are relevant domain keywords, but common natural phrasings ('reset the breaker', 'why is my provider stuck') and variations are missing, matching the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The CLI resilience-management niche is distinct and specific, making it unlikely to trigger for the wrong skill, matching the score-3 anchor.	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-resilience/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.