pinggy-tunnel

# Pinggy Tunnel Skill Expose a local service (dev server, webhook receiver, MCP endpoint, demo) to the public internet using a Pinggy SSH reverse tunnel. No daemon to install — the user's stock SSH client connects to `a.pinggy.io:443` and Pinggy hands back a public HTTP/HTTPS URL. Free tier: 60-minute tunnels, random subdomain, no signup. Pro tier ($3/mo) is an opt-in with a token. ## When to Use - User asks to "expose this locally", "share my dev server", "make this URL public", "tunnel port N", "get a public URL for a webhook" - Need to receive a webhook callback during a local task (Stripe, GitHub, Discord, AgentMail) - Sharing a one-off HTTP demo (MCP server, Ollama/vLLM endpoint, dashboard) with a remote party - The host has SSH but no `cloudflared` / `ngrok` binary, and installing one would be overkill If the host already has `cloudflared` configured, prefer the `cloudflared-quick-tunnel` skill — Cloudflare quick tunnels don't expire after 60 minutes. ## Prerequisites - `ssh` on PATH (`ssh -V`). Default on Linux, macOS, and Windows 10+. No other install. - A local service listening on `127.0.0.1:<port>` before the tunnel starts. Pinggy will return URLs but they'll 502 until the local origin is up. Optional: - `PINGGY_TOKEN` env var for paid Pro features (persistent subdomain, custom domain, multiple tunnels, no 60-minute cap). Free tier needs no credentials. ## Quick Reference ```bash # Plain HTTP/HTTPS tunnel for port 8000 (free tier) ssh -p 443 -o StrictHos...