omni-combos-routing

Create and manage routing combos with 19 strategies (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.

Quality

58%

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/omni-combos-routing/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.

The body offers actionable, executable curl examples and a useful strategy table, but suffers from duplicated endpoint listings, empty placeholder payloads, and no validation guidance around destructive operations. Progressive disclosure is limited by the absence of bundle reference files.

Suggestions

Remove the duplicated auto-generated endpoint block or merge it with the curated section to eliminate repeated curl examples and empty `-d '{}'` payloads.

Add a short create-then-test-then-activate workflow with a validation checkpoint (e.g., call /api/combos/test before enabling) for destructive/batch operations.

Move the full endpoint reference into a references/ file (or rely on the linked OpenAPI spec) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept over-explanation, but it duplicates endpoint listings (auto-generated section plus a curated section repeat the same /api/combos curls) and carries empty `-d '{}'` payloads that could be trimmed.	3 / 5
Actionability	The curated section provides concrete, executable curl examples with real payloads (create combo with targets, auto-combo, simulate, toggle); the auto-generated section's empty `-d '{}'` bodies are the main minor gap.	4 / 5
Workflow Clarity	The skill is reference-style with no sequenced workflow, and destructive/batch operations (DELETE combo, DELETE fallback chain, reorder) lack validation or feedback loops, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Section headers and a pointer to the OpenAPI spec provide some structure, but the bulk API reference is inlined in SKILL.md with no bundle files, so content that could live in a separate reference file is not split out.	3 / 5
	Total	13 / 20 Passed

Description

58%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 conveys a clear, multi-action 'what' for a well-scoped routing niche but omits any explicit 'when to use' trigger guidance and relies on jargon-heavy terms. It is specific and distinct yet incomplete on activation cues.

Suggestions

Append an explicit 'Use when ...' clause naming natural trigger phrases (e.g., 'Use when configuring model routing, fallback chains, or load balancing across providers').

Add user-natural synonyms alongside the technical strategy names so the description matches how users actually phrase the need.

Mention the activate/deactivate and dry-run/simulate capabilities to close the coverage gaps.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Create and manage routing combos', 'Configure fallback chains', 'test routing outcomes', 'retrieve combo metrics' — with minor gaps (activate/deactivate, simulate, MCP not mentioned).	4 / 5
Completeness	The 'what' is clearly stated (combos, strategies, fallback chains, testing, metrics) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Contains relevant domain terms ('routing combos', 'fallback chains', 'priority', 'weighted', 'round-robin') but they lean technical and lack common synonyms or natural user phrasings.	3 / 5
Distinctiveness Conflict Risk	Targets a fairly specific niche (routing combos with 19 strategies) that is mostly distinct from other skills, with only minor overlap risk against general routing/load-balancing skills.	4 / 5
	Total	14 / 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/omni-combos-routing/SKILL.md
Commit: c3945a7

Reviewed: 3 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.