CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/omni-version-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable — every endpoint has an executable curl example — but it is repetitive in its request templates and monolithic in structure, with no bundle files or progressive disclosure. Workflow sequencing for destructive operations lacks validation checkpoints.

Suggestions

Collapse the repeated curl blocks into one canonical example plus a table of method/path/payload triples to remove ~20 duplicated request templates.

Add explicit validation/verification steps for destructive or state-changing operations (e.g., after update or rotate-key, call GET /status to confirm the service is running with the new version/key).

Move the per-endpoint reference detail into a bundled references file (e.g., references/endpoints.md) and keep SKILL.md as a concise overview that links to it, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Prose descriptions are terse, but the identical curl template (host, two headers, `-d '{}'`) is repeated ~20 times across endpoints; showing the common pattern once plus a path table would be tighter, so it is mostly efficient with unnecessary repetition.

2 / 3

Actionability

Every endpoint ships a concrete, copy-paste-ready curl command with the correct method, host, auth header, and body, matching the anchor for fully executable, copy-paste-ready examples.

3 / 3

Workflow Clarity

Multi-step operations such as update ("Stops the service... installs the newer npm version, then restarts") and rotate-key have a sequence, but no validation or verification checkpoints are mentioned for these destructive/state-changing ops, capping workflow clarity at 2.

2 / 3

Progressive Disclosure

The body is a monolithic ~395-line inline API reference that could live in a separate file, with only a single external pointer to the OpenAPI spec; structure exists per service but content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

60%

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 about what the skill does, but it omits any "Use when..." trigger guidance and leans on jargon product names, leaving the when-to-use question only implied. Distinctiveness is moderate due to generic service-lifecycle verbs.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g., "Use when the user wants to install, start, or manage local 9Router or CLIProxyAPI services, or check their status and logs").

Broaden trigger terms beyond product names to include phrasings users actually say, such as "manage local services", "check if a service is running", or "pull service logs".

Reconcile the service list with the body (which also covers Mux and Bifrost) so the description does not under-claim scope.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — "Install, start, stop, restart, and update", "Monitor service status, retrieve logs", and "configure auto-start" — matching the anchor that lists multiple specific concrete actions.

3 / 3

Completeness

It clearly answers "what" but has no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Keywords like install/start/stop/restart/update services, monitor status, and retrieve logs are natural, but the trigger terms are anchored to jargon product names (9Router, CLIProxyAPI) and lack common user phrasings, so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The embedded-service lifecycle niche is somewhat specific, but generic verbs like start/stop/restart services could overlap with other service-management skills, and the description omits two of the four services the body covers.

2 / 3

Total

9

/

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.