Official agent skill

Gateway Proxy Debug

by vercel-labs in vercel-labs/vercel-openclaw-archived

Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth.

OfficialMITAuto-check passedBackend & APIs

Install Gateway Proxy Debug

skills CLI

$ npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vercel-labs/vercel-openclaw-archived gateway-proxy-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gateway-proxy-debug .claude/skills/gateway-proxy-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gateway-proxy-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug into .claude/skills/gateway-proxy-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gateway-proxy-debug", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vercel-labs/vercel-openclaw-archived gateway-proxy-debug --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/gateway-proxy-debug .agents/skills/gateway-proxy-debug && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gateway-proxy-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug into .agents/skills/gateway-proxy-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gateway-proxy-debug", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vercel-labs/vercel-openclaw-archived gateway-proxy-debug --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/gateway-proxy-debug .cursor/skills/gateway-proxy-debug && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gateway-proxy-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug into .cursor/skills/gateway-proxy-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gateway-proxy-debug", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/vercel-labs/vercel-openclaw-archived.git --path .agents/skills/gateway-proxy-debug

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vercel-labs/vercel-openclaw-archived gateway-proxy-debug --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/gateway-proxy-debug .gemini/skills/gateway-proxy-debug && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gateway-proxy-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug into .gemini/skills/gateway-proxy-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gateway-proxy-debug", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install vercel-labs/vercel-openclaw-archived gateway-proxy-debug

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/gateway-proxy-debug .github/skills/gateway-proxy-debug && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gateway-proxy-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug into .github/skills/gateway-proxy-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gateway-proxy-debug", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vercel-labs/vercel-openclaw-archived gateway-proxy-debug --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/gateway-proxy-debug .opencode/skills/gateway-proxy-debug && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gateway-proxy-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/gateway-proxy-debug into .opencode/skills/gateway-proxy-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gateway-proxy-debug", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gateway-proxy-debug
GitHub stars: 117
Token cost: ~573 tokens
SKILL.md length: 196 words
Files: 1
Skills in repo: 16
Repo updated: May 15, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth.

The OpenClaw UI
SKILL.md covers Evidence First, Path Diagram, Common Failure Splits and Fix Boundaries, plus 1 more section
Calls node
Gateway proxying

What it does

Gateway Proxy Debug is an agent skill from vercel-labs/vercel-openclaw-archived, published by the product's own GitHub organization. Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Use when the OpenClaw UI, WebSockets, gateway proxying, or waiting-page flow breaks.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Realtime and WebSockets and Debugging. It works with Vercel. The repository describes itself as: Deploy OpenClaw on Vercel. The licence is MIT.

When your agent uses it

The OpenClaw UI
Gateway proxying
Waiting-page flow breaks

Example prompts

“/gateway-proxy-debug”

What it can do on your machine

Read from SKILL.md and the folder at commit d592f7b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gateway Proxy Debug loads about 573 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 196 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~75
When it runs · the whole SKILL.md, loaded when a task matches: ~573

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vercel-labs/vercel-openclaw-archived at commit d592f7b, republished under its MIT licence (© vercel-labs). 196 words, ~573 tokens.

Download SKILL.mdSave it as .claude/skills/gateway-proxy-debug/SKILL.md (or your agent's skills folder).

name: gateway-proxy-debug
description: Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Use when the OpenClaw UI, WebSockets, gateway proxying, or waiting-page flow breaks.

Gateway Proxy Debug

Use this skill when the wrapper can reach a sandbox but /gateway, HTML injection, WebSockets, or token handoff is broken.

Evidence First

Collect:

Browser URL and failing request path.
GET /api/status.
GET /api/admin/sandbox-diag.
GET /api/admin/logs filtered for proxy., gateway., sandbox.port_, token..
Network trace for /gateway/*, WebSocket upgrade, and POST /api/status heartbeat.

Keep app auth, deployment protection bypass, gateway token, and AI Gateway auth separate. Do not paste gateway tokens in artifacts.

Path Diagram

text

browser -> wrapper auth -> /gateway route -> ensure sandbox running
  -> fresh gateway token -> sandbox port URL -> OpenClaw gateway
  -> HTML injection -> WebSocket rewrite -> heartbeat POST /api/status

Mark each edge unknown, verified-good, or verified-bad.

Common Failure Splits

Waiting page is correct because sandbox is not ready yet.
Proxy auth failed before any sandbox request.
Cached port URL is stale and needs invalidation.
Gateway token is stale or not injected.
HTML injection failed or produced a malformed script.
WebSocket URL rewrite points at the wrong origin/path.
Heartbeat is missing and sandbox times out.

Fix Boundaries

Primary: src/app/gateway/[[...path]]/route.ts.
Helpers: src/server/proxy/{proxy-route-utils,htmlInjection,waitingPage}.ts.
Lifecycle dependencies: src/server/sandbox/lifecycle.ts, src/server/public-url.ts.
Tests: proxy/html injection tests plus lifecycle tests for heartbeat interactions.
Docs: lat.md/sandbox-lifecycle.md, docs/architecture.md, docs/deployment-protection.md.

Verification

Run focused tests when available, then:

bash

node scripts/verify.mjs --steps=test,typecheck
lat check

For UI/WebSocket fixes, verify in a browser or with a smoke check that HTML contains the injected script and WebSocket traffic reaches the sandbox.

Files

Just SKILL.md in .agents/skills/gateway-proxy-debug of vercel-labs/vercel-openclaw-archived.

Open the folder on GitHubat commit d592f7b

Compare with similar skills

Gateway Proxy Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gateway Proxy Debug compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gateway Proxy Debug this skillvercel-labs/vercel-openclaw-archived	117	—	~573	Automated safety check: Pass	MIT	4 mo ago
Supabase Development and Debuggingsupabase/agent-skills	2.7k	3 repos	~3.6k	Automated safety check: Pass	MIT	6 days ago
Debugging Websocket IssuesAgentWorkforce/relay	866	1 repos	~1.3k	Automated safety check: Pass	Apache-2.0	today
Nitro Server Toolkitantfu/skills	5.9k	—	~948	Automated safety check: Pass	MIT	8 days ago
Debug Logsadam-s/intercept	189	—	~1.1k	Automated safety check: Pass	MIT	2 mo ago
Realtimebutterbase-ai/butterbase-skills	534	—	~2.1k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Supabase Development and Debugging
supabase/agent-skills
Official
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
2.7k GitHub starsUsed in 3 repos~3.6k tokens
Backend & APIsAuto-check passed
Debugging Websocket Issues
AgentWorkforce/relay
A skill your agent uses when seeing WebSocket errors like "Invalid frame header", "RSV1 must be clear", or "WSERRUNEXPECTEDRSV1" - covers multiple WebSocketServer conflicts, compression issues, and…
866 GitHub starsUsed in 1 repo~1.3k tokens
Backend & APIsAuto-check passed
Nitro Server Toolkit
antfu/skills
Reference for Nitro v3, the server toolkit behind Nuxt: file routing, route rules, caching, storage, tasks, websockets and deployment presets.
5.9k GitHub stars~948 tokensUpdated 8 days ago
Backend & APIsAuto-check passed
Debug Logs
adam-s/intercept
Iterative debugging with targeted logs. An agent skill from adam-s/intercept.
189 GitHub stars~1.1k tokensUpdated 2 mo ago
Backend & APIsAuto-check passed
Realtime
butterbase-ai/butterbase-skills
A skill your agent uses when enabling WebSocket subscriptions for live database changes, presence/multiplayer state, or when debugging clients that connect but receive no events
534 GitHub stars~2.1k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
Vercel Functions
vercel/vercel-plugin
Official
Vercel Functions expert guidance — Node.js/Bun/Python runtimes, Fluid Compute, long-duration (30 min) functions, large functions (5 GB bundles), Docker/OCI container images, plan limits, streaming…
301 GitHub stars~12k tokensUpdated today
Backend & APIsAuto-check: notes

More from vercel-labs/vercel-openclaw-archived

All 16 skills in this repo

Channel Debug Core
vercel-labs/vercel-openclaw-archived
Official
Channel webhook triage for vercel-openclaw Slack/Telegram/Discord/WhatsApp issues: prove deployment state, collect admin readiness endpoints, build evidence-first handoff before fixes.
117 GitHub stars~2k tokensUpdated 4 mo ago
Auto-check: notes
Lat Md
vercel-labs/vercel-openclaw-archived
Official
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs.
117 GitHub starsUsed in 1 repo~1.2k tokens
Auto-check passed
Cron Watchdog Debug
vercel-labs/vercel-openclaw-archived
Official
Cron and watchdog debugging for vercel-openclaw: Vercel Cron auth, persisted OpenClaw jobs, cron wake keys, token refresh, restore oracle, hot spare, and watchdog reports.
117 GitHub stars~1.6k tokensUpdated 4 mo ago
Auto-check passed
Auth Store Debug
vercel-labs/vercel-openclaw-archived
Official
Auth and store debugging for vercel-openclaw: admin-secret mode, Sign in with Vercel, session cookies, CSRF, LOCALREADONLY, Redis vs memory store, keyspace namespacing, and metadata shape migrations.
117 GitHub stars~465 tokensUpdated 4 mo ago
Auto-check passed
Firewall AI Gateway Debug
vercel-labs/vercel-openclaw-archived
Official
Firewall and Vercel AI Gateway debugging for vercel-openclaw: network policy allowlists, OIDC token refresh, AI Gateway transform rules, firewall learning/enforcement, and sandbox.update…
117 GitHub stars~550 tokensUpdated 4 mo ago
Auto-check passed
Openclaw Bootstrap Debug
vercel-labs/vercel-openclaw-archived
Official
OpenClaw bootstrap, bundle, config, and restore-asset debugging for vercel-openclaw: openclaw.bundle sidecars, plugin discovery, channel catalog, restart scripts, config hashes, dynamic resume…
117 GitHub stars~494 tokensUpdated 4 mo ago
Auto-check passed

Works with

Vercel

Questions about Gateway Proxy Debug

What does Gateway Proxy Debug do?

Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Gateway Proxy Debug is an agent skill from vercel-labs/vercel-openclaw-archived, published by the product's own GitHub organization. Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth.

When should I use Gateway Proxy Debug?

Gateway Proxy Debug fits situations like: the OpenClaw UI; gateway proxying; waiting-page flow breaks.

How do I install Gateway Proxy Debug in Claude Code?

Run `npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a claude-code`. Or copy the skill folder (.agents/skills/gateway-proxy-debug in vercel-labs/vercel-openclaw-archived) into .claude/skills/gateway-proxy-debug in your project. Claude Code loads it when a task matches its description.

How do I install Gateway Proxy Debug in Codex?

Run `npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a codex`. Or copy the skill folder (.agents/skills/gateway-proxy-debug in vercel-labs/vercel-openclaw-archived) into .agents/skills/gateway-proxy-debug in your project. Codex loads it when a task matches its description.

Can I use Gateway Proxy Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel-labs/vercel-openclaw-archived --skill gateway-proxy-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gateway-proxy-debug, .gemini/skills/gateway-proxy-debug, .github/skills/gateway-proxy-debug and .opencode/skills/gateway-proxy-debug in your project.

What does Gateway Proxy Debug need to run?

Going by SKILL.md and its folder, Gateway Proxy Debug needs the command-line tools its instructions call (node).

Does Gateway Proxy Debug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gateway Proxy Debug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gateway Proxy Debug use?

Gateway Proxy Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gateway Proxy Debug use?

About 573 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gateway Proxy Debug?

Skills that share tags, products or a category with Gateway Proxy Debug: Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Debugging Websocket Issues (AgentWorkforce/relay, 866 stars), Nitro Server Toolkit (antfu/skills, 5.9k stars) and Debug Logs (adam-s/intercept, 189 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gateway Proxy Debug?

vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/vercel-openclaw-archived, which has 117 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on May 15, 2026.

Source: vercel-labs/vercel-openclaw-archived on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gateway Proxy Debug

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Gateway Proxy Debug

Evidence First

Path Diagram

Common Failure Splits

Fix Boundaries

Verification

Files

Compare with similar skills

Similar skills

More from vercel-labs/vercel-openclaw-archived

Related

Questions about Gateway Proxy Debug