CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omni-version-manager

Install, start, stop, restart, and update embedded services (9Router, CLIProxyAPI). Monitor service status, retrieve logs, and configure auto-start for local-only service endpoints.

Quality

72%

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/omni-version-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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.

Excellent progressive disclosure — a clean index where every link resolves to a well-organized reference file with executable curl examples — and good token efficiency with no padding. The weaknesses are the absence of any executable example or base URL in the body itself and the total lack of a service-lifecycle workflow with verification steps for state-changing operations.

Suggestions

Add a short quick-start snippet in the body with the base URL and one end-to-end example (e.g., install 9Router, start it, then GET status to confirm it is running) so the skill is executable without first opening the reference.

Document the common service lifecycle as an ordered workflow — install → start → verify via GET status → check logs on failure — with an explicit verification checkpoint, since operations like install, update, and stop are state-changing.

Condense the 76-line endpoint list by stating the shared verb pattern (install/start/stop/restart/update/status/auto-start/auto-restart-adopted apply to each service) and linking once per service, trimming several hundred tokens.

DimensionReasoningScore

Conciseness

The body is lean with zero concept explanation — the Authentication section is two sentences and the Payloads section is a one-line pointer, assuming Claude's competence. It is not a 5 because the Overview repeats the frontmatter description verbatim and the 76-line endpoint list is highly repetitive (8 services × ~8 verbs) and could be compressed to a stated verb pattern per service.

4 / 5

Actionability

The body provides concrete endpoint paths and a concrete auth mechanism ("Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false"), but contains no executable example — no base URL/port and no sample request, which live only in the linked reference file. This matches the some-concrete-guidance-but-incomplete anchor rather than the mostly-executable anchor.

3 / 5

Workflow Clarity

The body is a flat endpoint catalog with no lifecycle sequence (e.g., install → start → verify status) and no validation checkpoints for state-changing operations like install, update, or stop. A rough ordering is only implied by the per-service verb sets, matching the rough-sequence-with-many-gaps anchor rather than anchor 1, since the per-endpoint reference does document each operation individually.

2 / 5

Progressive Disclosure

The body is a clear overview with a single, one-level-deep reference: all 76 "references/endpoints.md#..." links resolve to real headings in the bundle file, which itself has a table of contents and per-endpoint curl examples. This exactly matches the well-signaled one-level-deep-references anchor with easy navigation and appropriately split content.

5 / 5

Total

14

/

20

Passed

Description

71%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 strong, action-dense description with excellent specificity and good natural keyword coverage anchored by distinctive product names. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness, and limited synonym coverage beyond the two named services.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to install, restart, update, or check the status of embedded services like 9Router, CLIProxyAPI, mux, bifrost, or singbox, or when retrieving service logs or configuring auto-start."

Include natural synonym phrasings users might say — "deploy", "upgrade", "service daemon", "process management" — to broaden trigger coverage beyond the literal verb list.

Mention the other managed services (mux, openwa, bifrost, dario, llmlingua, singbox) or a collective phrase like "and other embedded services" so the description covers the skill's actual scope.

DimensionReasoningScore

Specificity

The description lists eight concrete actions — "Install, start, stop, restart, and update", "Monitor service status, retrieve logs, and configure auto-start" — covering the full service lifecycle, matching the comprehensive multi-action anchor. It does not fit anchor 4 because there is no evident gap in the action coverage within its stated scope.

5 / 5

Completeness

The "what" is clearly answered with concrete actions, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("install", "restart", "service status", "logs", "auto-start", plus product names 9Router and CLIProxyAPI), matching the good-coverage anchor. It falls short of 5 because synonyms and variations users might actually say (e.g., "deploy", "upgrade", "daemon", "process") and the other managed services (mux, bifrost, singbox, etc.) are missing.

4 / 5

Distinctiveness Conflict Risk

Naming specific products ("9Router, CLIProxyAPI") and the niche of "embedded services" and "local-only service endpoints" gives it a mostly distinct trigger profile. It is not a 5 because the generic lifecycle verbs (install/start/stop) overlap with any generic service- or process-management skill, and the absence of explicit trigger phrases weakens distinct triggering.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

diegosouzapw/OmniRoute

Path

skills/omni-version-manager/SKILL.md

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.