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

53%

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

Quality

Content

41%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.

This is a thin auto-generated stub: structurally clean and token-efficient, but it provides almost no executable guidance for the skill's actual purpose and contains no tunnel-creation workflow. It reads as scaffolding awaiting real content rather than a finished skill body.

Suggestions

Add concrete, copy-paste-ready tunnel commands (e.g. ngrok and cloudflared invocations) under a Quick start section to fix the low actionability.

Provide a sequenced workflow with validation checkpoints (create tunnel -> verify reachable -> tear down) to address workflow_clarity.

Replace the "No endpoints mapped for this area yet." placeholder with real endpoint guidance or remove it to tighten conciseness and structure.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude already knows; however the generator comment and the empty "No endpoints mapped for this area yet." placeholder are minor noise that keep it just short of a 5.	4 / 5
Actionability	Only tangential concrete guidance is present (the `POST /api/auth/login` endpoint and `REQUIRE_API_KEY=false` flag); the core task of actually creating/managing tunnels has no commands, code, or steps, so specific execution guidance is missing.	2 / 5
Workflow Clarity	There is no sequence of steps whatsoever for creating or managing tunnels and no validation checkpoints; the body is a set of section stubs rather than a workflow, matching the "steps missing" anchor.	1 / 5
Progressive Disclosure	Sections are clearly organized (Overview, Authentication, Endpoints, Payloads) and the body points one level deep to `docs/openapi.yaml` for detailed schemas; the empty Endpoints placeholder is a minor organization gap.	4 / 5
	Total	11 / 20 Passed

Description

66%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.

A specific, tool-named description that clearly conveys what the skill does, but it lacks an explicit "Use when..." trigger clause, which limits its completeness score. Trigger terms are strong and it is reasonably distinct from sibling skills.

Suggestions

Add an explicit "Use when..." clause (e.g. "Use when you need to expose OmniRoute to the internet or share access with remote agents or CI pipelines") to raise completeness.

Expand the action verbs beyond "create and manage" (e.g. inspect, rotate, tear down tunnels) to improve specificity coverage.

Include a couple more natural trigger synonyms such as "port forwarding" or "public URL" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ("Create and manage secure tunnels") and enumerates specific tools (ngrok, Cloudflare Tunnel, custom) plus concrete targets (expose to internet, share with remote agents/CI pipelines), with only minor gaps in what "manage" entails.	4 / 5
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance; the "to expose... or share access..." purpose clause only weakly implies when, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural user-facing terms like "secure tunnels", "ngrok", "Cloudflare Tunnel", "expose to the internet", and "share access" with good synonym coverage, though a few common variants (e.g. port forwarding, localtunnel) are absent.	4 / 5
Distinctiveness Conflict Risk	The OmniRoute framing and named tunneling tools carve a fairly distinct niche with minimal conflict risk, though "expose to the internet" could mildly overlap with general networking skills.	4 / 5
	Total	15 / 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-tunnels/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.