CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-health

Check server health, component status, and live metrics from the CLI. Run `health`, `health components`, and `health watch` for a real-time dashboard of circuit breakers and provider status.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 clean, actionable CLI command reference with well-organized sections and no unnecessary concept explanations or deep references; its only minor weakness is the Overview duplicating the frontmatter description.

DimensionReasoningScore

Conciseness

The body is a lean command reference — subcommands, flags, and short executable examples with no explaining of concepts Claude already knows; the only slack is the Overview line repeating the frontmatter description verbatim, which is minor relative to the level-2 anchor's broader unnecessary explanation.

3 / 3

Actionability

Provides copy-paste-ready executable commands ('npm install -g omniroute', 'omniroute doctor', 'omniroute health components', 'omniroute health watch') alongside enumerated flags, matching the fully-executable level-3 anchor rather than the pseudocode/abstract lower anchors.

3 / 3

Workflow Clarity

This is a single-purpose read-only CLI reference with each subcommand unambiguously documented (purpose, flags, example); per the simple-skills scoring note no multi-step sequence or validation checkpoint is required, so it clears the level-3 bar rather than the gap-laden level-2 anchor.

3 / 3

Progressive Disclosure

No bundle files exist and none are referenced; the body is self-contained and organized into clear one-level sections (Overview, Quick install, per-subcommand Subcommands) with no nested references, matching the well-organized level-3 anchor rather than the monolithic or nested-reference lower anchors.

3 / 3

Total

12

/

12

Passed

Description

82%

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 with good natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when checking whether OmniRoute or its providers are healthy, or when the user mentions circuit breakers, provider status, or a live health dashboard.'

Name the tool ('omniroute') in the description so the trigger is unambiguous and less likely to conflict with other health-checking skills.

DimensionReasoningScore

Specificity

Quotes 'Check server health, component status, and live metrics' and the explicit commands 'health', 'health components', and 'health watch' — multiple concrete actions, matching the anchor for listing several specific concrete actions rather than the level-2 single-domain example.

3 / 3

Completeness

The 'what' is explicit (check health/components/metrics, run the three subcommands), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2 rather than reaching the level-3 both-what-and-when anchor.

2 / 3

Trigger Term Quality

Natural monitoring terms a user would actually say — 'server health', 'component status', 'live metrics', 'health watch', 'circuit breakers', 'provider status' — give good coverage; not the jargon-only or sparse-variation cases that anchor levels 1 and 2.

3 / 3

Distinctiveness Conflict Risk

The niche is distinct — CLI server-health monitoring of 'circuit breakers and provider status' — unlikely to trigger for unrelated skills, matching the clear-niche level-3 anchor rather than the generic overlap-prone lower anchors.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
diegosouzapw/OmniRoute
Reviewed

Table of Contents

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.