omni-proxies

Configure HTTP/HTTPS/SOCKS proxies for upstream provider requests. Set per-provider or global proxy rules, test connectivity, and manage proxy rotation.

Quality

37%

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-proxies/SKILL.md

Quality

Content

36%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 a thin auto-generated stub that duplicates the description and points to an external OpenAPI spec without providing any executable proxy-configuration guidance, workflow, or in-skill references. It is concise but lacks actionable content and navigable structure.

Suggestions

Add concrete, executable guidance such as example proxy configuration values, curl/test commands, and per-provider override examples instead of only pointing to the OpenAPI spec.

Provide a sequenced workflow with a connectivity-validation checkpoint (configure -> test -> rotate) so the proxy setup process is clear and errors are caught early.

Create a references/ file for detailed payload/endpoint schemas and link to it with one-level-deep navigation rather than leaving 'No endpoints mapped for this area yet'.

Dimension	Reasoning	Score
Conciseness	The body is short and does not over-explain concepts Claude already knows, though it restates the description verbatim in the Overview and the Payloads line points elsewhere without adding value.	4 / 5
Actionability	It provides almost no executable guidance: no commands, code, or concrete proxy settings, just pointers to an external OpenAPI spec and the vague 'No endpoints mapped for this area yet' note.	2 / 5
Workflow Clarity	There is no sequenced workflow for configuring, testing, or rotating proxies, and no validation steps for connectivity testing despite this being a batch/risk-relevant operation.	2 / 5
Progressive Disclosure	The body is essentially a stub that defers all real content to an external OpenAPI spec with no bundle files present and no in-skill structure to navigate, making it effectively unnavigable.	1 / 5
	Total	9 / 20 Passed

Description

38%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 clearly conveys what the skill does with concrete actions, but it omits any explicit 'Use when...' trigger guidance and leans heavily on technical jargon, weakening trigger-term quality and completeness. It occupies a reasonably distinct niche but would benefit from natural-language trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when routing upstream API requests through a proxy, debugging connectivity, or configuring proxy rotation').

Replace jargon-heavy phrasing with terms users actually say (e.g. 'route requests through a proxy', 'outbound HTTP/SOCKS proxy') to improve trigger-term coverage.

Add synonyms and concrete protocols/file references to broaden keyword coverage and reduce overlap with generic networking skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Configure HTTP/HTTPS/SOCKS proxies', 'Set per-provider or global proxy rules, test connectivity, and manage proxy rotation'), but lacks detail on how rotation or testing work, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is stated clearly but there is no 'Use when...' trigger clause or equivalent explicit guidance on when Claude should invoke it, which caps completeness at 3 and the absence pushes it down.	2 / 5
Trigger Term Quality	It is dominated by technical jargon ('upstream provider requests', 'per-provider or global proxy rules') with almost no natural phrases a user would say when needing this skill, such as 'proxy', 'route through', or 'outbound proxy'.	2 / 5
Distinctiveness Conflict Risk	It targets a fairly specific niche (proxy configuration for upstream providers), but the lack of explicit trigger phrases leaves moderate overlap risk with general networking or provider-request skills.	3 / 5
	Total	11 / 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-proxies/SKILL.md
Commit: ea0cdc5

Reviewed: about 6 hours 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.