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

60%

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

Quality

Content

37%

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

The body is token-efficient and sectioned, but it carries essentially no actionable content for configuring proxies — endpoints are unmapped and the reader is redirected to the OpenAPI spec. It reads as an auto-generated stub rather than usable guidance.

Suggestions

Replace the empty Endpoints section with concrete proxy configuration steps or endpoint examples (e.g. how to set a per-provider proxy and verify it).

Add a short workflow with a validation checkpoint for the 'test connectivity' step so the configure→verify loop is explicit.

Move the OpenAPI pointer into a clearly signaled reference and ensure the Overview itself summarizes the key proxy operations instead of only restating the description.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence with no concept over-explanation — sections like '## Overview' and '## Authentication' state only essentials; not 2 because there is no padding to tighten.	3 / 3
Actionability	No executable guidance for the core task: '## Endpoints' states '_No endpoints mapped for this area yet._' and '## Payloads' only says 'See the full OpenAPI specification…', describing rather than instructing; not 2 because there is no concrete code or command at all.	1 / 3
Workflow Clarity	There is no sequence for the configure→test→rotate proxy flow and no validation checkpoints, despite testing connectivity being a multi-step risky operation; not 2 because steps are absent entirely, not merely implicit.	1 / 3
Progressive Disclosure	Sections exist and the OpenAPI reference is signaled one level deep, but the body is largely placeholder ('_No endpoints mapped for this area yet._') with no bundle files, so organization is incomplete; not 3 because it is not a clear, well-organized overview, not 1 because it is not a monolithic wall or deeply nested.	2 / 3
	Total	7 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description with concrete actions and natural trigger terms, but it omits any explicit 'Use when…' guidance for when Claude should activate it. Adding a trigger clause would raise the completeness dimension.

Suggestions

Append a 'Use when…' clause naming the situations that should activate this skill (e.g. proxy setup, connectivity issues, rotating upstream proxies).

Add common user phrasings like 'set up a proxy', 'SOCKS proxy', or 'provider proxy rotation' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure HTTP/HTTPS/SOCKS proxies', 'Set per-provider or global proxy rules', 'test connectivity', 'manage proxy rotation' — matching the multiple-specific-actions anchor; not the level below because it names more than a domain and a single action.	3 / 3
Completeness	Clearly states what the skill does but offers no 'Use when…' or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2; not 3 because the 'when' is entirely absent, not 1 because the 'what' is explicit and specific.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered — 'proxies', 'HTTP/HTTPS/SOCKS proxies', 'proxy rotation', 'connectivity' — rather than generic jargon; not below because common variations are present rather than missing.	3 / 3
Distinctiveness Conflict Risk	A clear niche — proxy configuration for upstream provider requests — unlikely to overlap with unrelated skills; not 2 because the domain is specific rather than broadly generic.	3 / 3
	Total	11 / 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-proxies/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.