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.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Omni Tunnels when an AI agent needs a reusable SKILL.md workflow for this job: Create and manage secure tunnels (ngrok, Cloudflare Tunnel, custom) to expose OmniRoute to the internet or share access with remote agents and CI pipelines.
When not to use it
Skip Omni Tunnels when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/omni-tunnels # Save SKILL.md to ~/.claude/skills/omni-tunnels/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-tunnels/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-tunnels/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Omni Tunnels skill for this task: Use Omni Tunnels when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
Create and manage secure tunnels (ngrok, Cloudflare Tunnel, custom) to expose OmniRoute to the internet or share access with remote agents and CI pipelines.
## Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via `POST /api/auth/login` or configure `REQUIRE_API_KEY=false` for local development.
## Endpoints
### GET /api/tunnels/cloudflared
GET tunnels › cloudflared
```bash curl http://localhost:20128/api/tunnels/cloudflared \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/tunnels/cloudflared
POST tunnels › cloudflared
```bash curl -X POST http://localhost:20128/api/tunnels/cloudflared \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/tunnels/ngrok
GET tunnels › ngrok
```bash curl http://localhost:20128/api/tunnels/ngrok \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/tunnels/ngrok
POST tunnels › ngrok
```bash curl -X POST http://localhost:20128/api/tunnels/ngrok \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/tunnels/tailscale
GET tunnels › tailscale
```bash curl http://localhost:20128/api/tunnels/tailscale \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/tunnels/tailscale/check
GET tunnels › tailscale › check
```bash curl http://localhost:20128/api/tunnels/tailscale/check \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/tunnels/tailscale/disable
POST tunnels › tailscale › disable
```bash curl -X POST http://localhost:20128/api/tunnels/tailscale/disable \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/tunnels/tailscale/enable
POST tunnels › tailscale › enable
```bash curl -X POST http://localhost:20128/api/tunnels/tailscale/enable \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/tunnels/tailscale/install
POST tunnels › tailscale › install
```bash curl -X POST http://localhost:20128/api/tunnels/tailscale/install \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/tunnels/tailscale/login
POST tunnels › tailscale › login
```bash curl -X POST http://localhost:20128/api/tunnels/tailscale/login \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/tunnels/tailscale/start-daemon
POST tunnels › tailscale › start daemon
```bash curl -X POST http://localhost:20128/api/tunnels/tailscale/start-daemon \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
## Payloads
See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.
Intended uses
- Use Omni Tunnels when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.