Tessl • The management layer for AI agent skills

SkillPublic

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

71%

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-serve/SKILL.md

Quality

Content

57%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 dense, command-first reference that is highly executable but suffers from duplicated generated-vs-custom sections, unexplained flag lists, a destructive restore operation without verification, and monolithic inlining of admin material beyond the skill's serve scope. Splitting admin content into reference files and adding post-restore validation would address the weakest dimensions.

Suggestions

Add a verification step after 'omniroute restore' (e.g. run 'omniroute doctor' or 'omniroute status' and confirm providers/config before resuming traffic), since restore destructively overwrites config and the SQLite database.

Deduplicate the generated and custom sections: merge the two Install and two Errors sections, and either give the 'Subcommands' flags brief semantics or drop the bare flag lists in favor of the 'Admin lifecycle' coverage.

Move out-of-scope admin material (tunnels, backup/restore, provider setup, logs, autostart) into clearly signaled reference files, keeping SKILL.md focused on server start/stop/restart/daemon configuration per its name and description.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (command blocks, tables, one-line error-to-fix mappings, no explanations of known concepts), but it is noticeably duplicated: two install sections, a generated 'Subcommands' flags list that repeats the 'Admin lifecycle' coverage, and two separate 'Errors' sections could be merged and tightened.	3 / 5
Actionability	Nearly all guidance is copy-paste ready ('omniroute serve', 'omniroute doctor --json \| jq ...', env-var exports, a fully specified non-interactive setup command), but the 'Subcommands' flags (--tui, --ready-timeout, --max-restarts, etc.) are listed with no semantics and the serve example is bare rather than demonstrating flag usage.	4 / 5
Workflow Clarity	The quick-start sequence (start -> setup -> doctor) includes a validation checkpoint and reset-encrypted-columns shows dry-run-before-force, but 'omniroute restore' — a destructive overwrite of config and SQLite DB — has no validation/verification step, capping workflow clarity at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	No bundle files exist and section headers are clear with an explicit table of external skill links, but this ~320-line body inlines admin material (tunnels, backup/restore, provider setup, logs, autostart) that belongs in separate reference files for a skill named 'cli-serve'.	3 / 5
	Total	13 / 20 Passed

Description

70%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 product-scoped distinctiveness, but it completely lacks a 'when to use' trigger clause and misses common synonyms like 'launch' or 'run the server'. Adding an explicit 'Use when...' sentence would fix its main weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to start, stop, restart, or launch the OmniRoute server, change its port, enable daemon/tray mode, or open the dashboard.'

Include common natural synonyms such as 'launch' and 'run the server' so the description matches how users phrase the request.

Consider converting 'Manage daemon mode, port configuration, auto-recovery...' into distinct action verbs (e.g. 'Enable daemon mode, override the port, configure auto-recovery') for full specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Start, stop, and restart the OmniRoute server from the CLI') and specific managed features (daemon mode, port configuration, auto-recovery, tray, dashboard shortcut), but 'Manage...' bundles several capabilities under one generic verb, leaving minor gaps versus the comprehensive 5 anchor.	4 / 5
Completeness	The 'what' is clear and concrete (server lifecycle plus configuration management), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural domain keywords are present ('start', 'stop', 'restart', 'server', 'CLI', 'daemon', 'port', 'tray', 'dashboard'), but common variations users would say such as 'launch', 'run', or 'kill the server' are missing, matching the 'good coverage, a few natural terms missing' anchor rather than comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named product ('OmniRoute server') with a tight lifecycle niche (start/stop/restart, daemon, tray, dashboard); sibling OmniRoute skills cover different operations (providers, backup, evals), so conflict risk is minimal.	5 / 5
	Total	16 / 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-serve/SKILL.md
Revision: 5b3be70

Reviewed: 13 days ago

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.

cli-serve

Table of Contents

Is this your skill?