cli-serve

Start, stop, and restart the OmniRoute server from the CLI. Manage daemon mode, port configuration, auto-recovery, system tray integration, and the dashboard open shortcut.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable CLI reference with concrete commands and examples, held back by duplication between the generated and custom sections and by being a single monolithic file with no progressive disclosure into local reference files. Consolidating the duplicated lifecycle content and splitting large reference tables into referenced files would improve both conciseness and progressive disclosure.

Suggestions

Remove the duplication between the top "Subcommands" section and the "Admin lifecycle" section, keeping one canonical source for serve/stop/restart/dashboard.

Add descriptions to the bare flags in the Subcommands section (e.g. dashboard --url, --tui) or drop that section in favor of the fuller flag tables below.

Split the large admin reference (tunnels, backup, recovery, config) into a referenced bundle file linked from a concise overview to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command tables and examples, but the generated "Subcommands" section duplicates the later "Admin lifecycle" section and several flags (e.g. dashboard --url, --tui) are listed without descriptions, so it could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands (omniroute serve, doctor --json, non-interactive setup with env vars) with flag tables and per-subcommand examples.	3 / 3
Workflow Clarity	A quick-start sequence with a doctor verification step exists and destructive ops carry warnings, but the body is primarily a command catalog lacking consistent validate-fix-retry checkpoints across sections.	2 / 3
Progressive Disclosure	The file is well-sectioned with clearly signaled external skill links, but no local bundle files exist and a large amount of reference content is inline in one ~310-line file rather than split into one-level-deep references.	2 / 3
	Total	9 / 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.

A specific, branded capability description with concrete actions and low conflict risk, weakened by the absence of an explicit "Use when..." trigger clause and only moderate natural-term coverage. Adding a usage trigger would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when starting, stopping, or restarting the OmniRoute server, or configuring daemon mode, ports, auto-recovery, or the system tray."

Include common natural-term variations users might say (e.g. "run the server", "bring the server up/down") alongside the branded OmniRoute phrasing.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "Start, stop, and restart the OmniRoute server" plus "Manage daemon mode, port configuration, auto-recovery, system tray integration, and the dashboard open shortcut" — matching the multi-action anchor.	3 / 3
Completeness	It clearly answers "what" the skill does but provides no "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural verbs (start/stop/restart/server) are present but tightly bound to the branded "OmniRoute" name and missing common variations, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The branded OmniRoute server lifecycle niche with specific actions (daemon, tray, auto-recovery) is clearly distinguishable and unlikely to trigger the wrong skill.	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-serve/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.