omni-mcp

Connect to the OmniRoute MCP server (37 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 16 permission scopes.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/omni-mcp/SKILL.md

Quality

Content

62%

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 with concrete MCP client configs and a complete tool catalog, but it repeats the description verbatim and carries empty placeholder sections, and lacks an explicit setup/validation workflow. Progressive disclosure is reasonable but depends entirely on external links with no local bundle.

Suggestions

Remove the verbatim repeat of the description in the Overview and the empty '_No endpoints mapped for this area yet._' placeholder to tighten token efficiency.

Add a short explicit connection workflow with a validation checkpoint (e.g. after configuring, run `omniroute_get_health` to confirm connectivity before calling other tools).

Provide a local reference file (e.g. references/TOOLS.md) for the full tool catalog and link to it one level deep, improving progressive disclosure beyond external-only links.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (config snippets and a compact tool table earn their tokens) but repeats the frontmatter description verbatim in the Overview and includes empty placeholder sections ('_No endpoints mapped for this area yet._') that add noise without value.	2 / 3
Actionability	It provides fully executable config blocks for Claude Desktop and Cursor/VS Code, exact transport endpoints, concrete env vars (OMNIROUTE_URL, OMNIROUTE_KEY), and a complete tool-scope table with named tools, all copy-paste ready.	3 / 3
Workflow Clarity	Connection steps are implied via the config blocks and transports, but there is no explicit sequenced setup workflow or validation checkpoint (e.g. verifying the server responds after configuring), so checkpoints are implicit rather than stated.	2 / 3
Progressive Disclosure	It has clear sections and signals external detail via a one-level-deep link to the MCP-SERVER.md docs, but no bundle files exist so progressive disclosure relies solely on external links rather than a real bundle structure; organization is adequate but not exemplary.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 well-scoped to the OmniRoute MCP server but lacks an explicit 'Use when' trigger, which caps completeness and trigger-term quality at 2. It is concise and third-person, avoiding fluff and over-claims.

Suggestions

Add an explicit trigger clause, e.g. 'Use when connecting to the OmniRoute MCP server, calling its routing/cache/memory tools, or configuring MCP clients like Claude Desktop or Cursor.'

Include natural user-facing terms alongside the technical categories (e.g. 'MCP connection', 'Claude Desktop MCP config', 'route LLM requests') to broaden trigger-term coverage.

State at least one concrete user action (e.g. 'Call MCP tools and configure transports') rather than only naming tool scopes.

Dimension	Reasoning	Score
Specificity	It names a concrete domain (MCP server, 37 tools, SSE/stdio/HTTP transports, 16 permission scopes) but lists tool categories rather than concrete actions a user performs, so it stops at 'domain and some actions.'	2 / 3
Completeness	It answers 'what' clearly (connect to the OmniRoute MCP server, 37 tools across scopes) but provides no 'Use when...' trigger, so 'when' is only implied, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	'routing, cache, compression, memory, skills, providers, and audit tools' are relevant domain terms but are technical jargon users rarely utter verbatim; common natural variations are missing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The product name 'OmniRoute MCP server' and the specific tool/transport scope give it a recognizable niche, but the absence of explicit triggers means it could overlap with other MCP-connection skills.	2 / 3
	Total	8 / 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/omni-mcp/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.