omni-tunnels

Create and manage secure tunnels (ngrok, Cloudflare Tunnel, custom) to expose OmniRoute to the internet or share access with remote agents and CI pipelines.

Quality

48%

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-tunnels/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 content is concise and well-sectioned but substantively hollow: it provides no executable tunnel commands, no tunnel-creation workflow with validation checkpoints, and an empty Endpoints section that defers detail to an external spec.

Suggestions

Add concrete, copy-paste-ready tunnel commands for each provider (ngrok, Cloudflare Tunnel, custom) including auth and verification steps.

Provide a sequenced workflow (authenticate -> start tunnel -> verify connectivity) with an explicit validation checkpoint before declaring success.

Either populate the Endpoints section with the key endpoints or remove the empty placeholder and point readers to a concrete reference rather than the generic OpenAPI URL.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept-padding or explanations of things Claude already knows; every section is terse. The only mild redundancy is the Overview restating the description, but no verbosity is present.	3 / 3
Actionability	No executable tunneling commands appear (e.g. `ngrok http 8080` or `cloudflared` flags), the Endpoints section is explicitly empty, and guidance defers to an external OpenAPI spec rather than instructing, matching the vague/abstract anchor.	1 / 3
Workflow Clarity	There is no sequenced workflow for creating or managing a tunnel, and no validation/verification checkpoint for this multi-step, fragile operation, matching the missing-steps anchor.	1 / 3
Progressive Disclosure	Sections are organized and the OpenAPI reference is one-level and clearly signaled, but no bundle files exist and the references point to an external runtime spec rather than split skill content, leaving the disclosure structure thin.	2 / 3
	Total	7 / 12 Passed

Description

60%

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 names concrete tools and actions, but lacks an explicit 'when to use' trigger clause and only partially covers natural trigger-term variations, leaving it distinguishable but not maximally clear.

Suggestions

Add an explicit trigger clause, e.g. 'Use when exposing a local OmniRoute server to the internet, testing webhooks, or sharing access with remote agents/CI.'

Include more natural user-facing trigger terms like 'expose local server', 'public URL', 'port forwarding', or 'webhook testing'.

Tighten distinctiveness by leading with the tunneling-specific framing to reduce overlap with generic deployment/networking skills.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Create and manage secure tunnels') with specific tools (ngrok, Cloudflare Tunnel, custom) and concrete use cases (expose to internet, share access with remote agents/CI), matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers what the skill does but has no 'Use when...' clause or explicit trigger guidance; per the guidelines, a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms users say ('tunnels', 'ngrok', 'Cloudflare Tunnel') but misses common variations like 'expose local server', 'port forwarding', or 'webhook testing'; the 'remote agents and CI pipelines' framing is somewhat jargony.	2 / 3
Distinctiveness Conflict Risk	The named-tool tunneling niche is fairly specific, but 'expose to internet / share access' phrasing could overlap with deployment or general networking skills, so it is not a clear distinct niche.	2 / 3
	Total	9 / 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-tunnels/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.