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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-health/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 clean, well-structured CLI reference with executable examples and minimal padding, but flags lack descriptions and there is no guidance on how the subcommands relate or when to use each.

Suggestions

Add a short gloss for each flag (e.g. `--alerts-only` — show only active alerts) so the examples are fully self-explanatory.

Drop or condense the Overview since it duplicates the frontmatter description verbatim.

Add a one-line note in each subcommand section on when to prefer it (e.g. 'use `health watch` for ongoing monitoring').

DimensionReasoningScore

Conciseness

The body is lean with terse flag lists and one-line examples and avoids explaining concepts Claude already knows; the only padding is the Overview repeating the frontmatter description verbatim.

4 / 5

Actionability

Provides copy-paste-ready executable commands and flags per subcommand, but flags are listed without descriptions (e.g. `--no-liveness`, `--alerts-only`), leaving minor gaps in what each flag does.

4 / 5

Workflow Clarity

Each subcommand is a single, unambiguous read-only action with a clear example, satisfying the simple-skill exception; no validation checkpoints are needed for non-destructive health checks, but no sequencing guidance ties the commands together.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections per subcommand with no nested or buried references and no bundle files to navigate; slightly over 50 lines, otherwise a 5.

4 / 5

Total

16

/

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 actionable with good trigger-term coverage and a clear niche, but it omits any explicit 'Use when...' guidance, leaving the trigger context implicit and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when checking whether the OmniRoute server or its providers are healthy, or when diagnosing circuit-breaker trips.'

Include a couple of natural synonyms ('uptime', 'status check') to broaden trigger-term coverage.

Tie the commands to the scenarios that prompt them so the 'when' is as concrete as the 'what'.

DimensionReasoningScore

Specificity

Names concrete actions ('Check server health, component status, and live metrics') and specific commands (`health`, `health components`, `health watch`) with a clear dashboard target (circuit breakers, provider status), falling just short of comprehensive coverage.

4 / 5

Completeness

Provides a clear 'what' (health checks, component status, live metrics via CLI dashboard) but lacks any 'Use when...' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('server health', 'component status', 'live metrics', 'circuit breakers', 'provider status') with good coverage, though common synonyms like 'uptime' or 'status check' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a distinct niche (CLI server-health monitoring for circuit breakers/provider status) with mostly distinct triggers, though generic 'health/status' phrasing carries minor overlap risk with related ops skills.

4 / 5

Total

15

/

20

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.