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.

52

Quality

57%

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

40%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 an auto-generated, monolithic API catalog: executable curl examples make it actionable, but it is padded with repetition, has no validation steps for destructive operations, and inlines reference material that belongs in a separate file. Structuring and trimming would substantially improve it.

Suggestions

Move the per-endpoint reference into a separate file (e.g. references/endpoints.md) and keep SKILL.md as a concise overview with one-level-deep pointers, per progressive-disclosure best practice.

De-duplicate the repeated curl/auth/LOCAL_ONLY boilerplate — state the common base URL, auth header, and local-only constraint once, then list only per-endpoint differences.

Add validation/verification steps for destructive and state-changing operations (e.g. check status after start, confirm the key was rotated after rotate-key, verify an account was removed after DELETE).

DimensionReasoningScore

Conciseness

~620 lines repeat the same curl block, auth headers, and '-d {}' body across ~30 near-identical endpoints plus recurring 'LOCAL_ONLY — loopback only' boilerplate, which is noticeable padding rather than explanation of known concepts.

2 / 5

Actionability

Every endpoint ships an executable curl command with correct method, host, port, and auth header, but input-taking endpoints (alias deletion, version, auto-start toggle) all show the empty '-d {}' body without the real payload shape, leaving minor gaps.

4 / 5

Workflow Clarity

There is no multi-step workflow — only a flat per-endpoint catalog — and destructive operations (install/stop/rotate-key/delete accounts) have no validation or verification steps, matching the anchor where validation is absent and sequencing is missing.

2 / 5

Progressive Disclosure

A ~580-line endpoint reference that clearly belongs in a separate file is inlined into SKILL.md, and the pointer to the full OpenAPI spec is buried at the very end, fitting the anchor for minimal structure with inlined content and buried references.

2 / 5

Total

10

/

20

Passed

Description

75%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 distinctive, naming concrete actions and a clear service niche, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause would round it out.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when managing local embedded services like 9Router or CLIProxyAPI, or when the user asks to start/stop/update a service or fetch its logs').

Include common synonyms or phrasings users might say (e.g., 'service lifecycle', 'restart a stuck service') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions explicitly — 'Install, start, stop, restart, and update', 'Monitor service status, retrieve logs, and configure auto-start' — with comprehensive coverage, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Clearly answers 'what' the skill does but provides no 'Use when...' or equivalent trigger clause; per the rubric, a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Good coverage of natural action verbs users would say (install/start/stop/restart/update/monitor/logs), but lacks synonyms and generic variations beyond the literal verbs, so it falls just below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — embedded services named 9Router and CLIProxyAPI with local-only endpoints — giving distinct triggers and minimal conflict with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (626 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.