Testing
doorkeeper-gem/doorkeeper
Write correct and complete RSpec tests for Doorkeeper. An agent skill from doorkeeper-gem/doorkeeper.
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…
Install Firewall AI Gateway Debug
$ npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived firewall-ai-gateway-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/firewall-ai-gateway-debug .claude/skills/firewall-ai-gateway-debug && rm -rf skills-srcUse ~/.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/
Install the "firewall-ai-gateway-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debug into .claude/skills/firewall-ai-gateway-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firewall-ai-gateway-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 install https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debugType 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.
$ npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived firewall-ai-gateway-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/firewall-ai-gateway-debug .agents/skills/firewall-ai-gateway-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "firewall-ai-gateway-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debug into .agents/skills/firewall-ai-gateway-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firewall-ai-gateway-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.
$ npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived firewall-ai-gateway-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/firewall-ai-gateway-debug .cursor/skills/firewall-ai-gateway-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "firewall-ai-gateway-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debug into .cursor/skills/firewall-ai-gateway-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firewall-ai-gateway-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 https://github.com/vercel-labs/vercel-openclaw-archived.git --path .agents/skills/firewall-ai-gateway-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived firewall-ai-gateway-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/firewall-ai-gateway-debug .gemini/skills/firewall-ai-gateway-debug && rm -rf skills-srcUse ~/.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/
Install the "firewall-ai-gateway-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debug into .gemini/skills/firewall-ai-gateway-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firewall-ai-gateway-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.
$ gh skill install vercel-labs/vercel-openclaw-archived firewall-ai-gateway-debugInstalls 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).
$ npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ 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/firewall-ai-gateway-debug .github/skills/firewall-ai-gateway-debug && rm -rf skills-srcUse ~/.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/
Install the "firewall-ai-gateway-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debug into .github/skills/firewall-ai-gateway-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firewall-ai-gateway-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.
$ npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived firewall-ai-gateway-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/firewall-ai-gateway-debug .opencode/skills/firewall-ai-gateway-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "firewall-ai-gateway-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/firewall-ai-gateway-debug into .opencode/skills/firewall-ai-gateway-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firewall-ai-gateway-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
firewall-ai-gateway-debug- GitHub stars
- 117
- Token cost
- ~550 tokens
- SKILL.md length
- 199 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Firewall policy application fails
- SKILL.md covers Evidence First, Critical Splits, Invariants and Fix Boundaries, plus 1 more section
- Calls node
- Tasks that involve OAuth and OpenID Connect
What it does
Firewall AI Gateway Debug is an agent skill from vercel-labs/vercel-openclaw-archived, published by the product's own GitHub organization. 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 networkPolicy calls. Use when model calls, egress, token refresh, or firewall policy application fails.
Its SKILL.md is about 550 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 Development, covering OAuth and OpenID Connect and Debugging. It works with Vercel. The repository describes itself as: Deploy OpenClaw on Vercel. The licence is MIT.
When your agent uses it
- Firewall policy application fails
- Tasks that involve OAuth and OpenID Connect
- Tasks that involve Debugging
Example prompts
- “/firewall-ai-gateway-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
Firewall AI Gateway Debug loads about 550 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 199 words of instructions outside code blocks.
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). 199 words, ~550 tokens.
Download SKILL.mdSave it as
.claude/skills/firewall-ai-gateway-debug/SKILL.md (or your agent's skills folder).- name
- firewall-ai-gateway-debug
- description
- 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 networkPolicy calls. Use when model calls, egress, token refresh, or firewall policy application fails.
Firewall AI Gateway Debug
Use this skill for model-call failures, egress blocks, network policy drift, or AI Gateway token refresh problems.
Evidence First
Collect:
GET /api/admin/preflightor launch verification preflight evidence.GET /api/admin/logsfiltered forfirewall.,token.,gateway.,watchdog..GET /api/admin/sandbox-diag.- Current firewall mode and learned/allowed domains from admin surfaces.
- Sanitized model-call or gateway error body. Do not print Authorization tokens.
Critical Splits
- AI Gateway credential unavailable vs expired vs circuit-breaker-open.
- Static API key bypass vs OIDC token path.
- Firewall learning/allowlist issue vs model provider/API issue.
OPENAI_BASE_URLinside sandbox is present, while Authorization is injected by network policy transform.- Policy object shape changes when an AI Gateway token exists.
Invariants
- AI Gateway token never enters sandbox files or env.
ai-gateway.vercel.shstays allowed even in enforcing mode.- Token refresh applies
sandbox.update({ networkPolicy }); it should not rewrite config files or restart the gateway. - Public/admin display URLs must not expose deployment-protection bypass secrets.
Fix Boundaries
- Primary:
src/server/firewall/{domains,policy,state}.ts. - Token path:
src/server/sandbox/lifecycle.ts,src/server/deploy-preflight.ts. - Public URLs:
src/server/public-url.ts. - Tests: firewall policy tests, token refresh tests, launch-verify/preflight tests.
- Docs:
docs/environment-variables.md,docs/deployment-protection.md,lat.md/sandbox-lifecycle.md.
Verification
node scripts/verify.mjs --steps=test,typecheck
lat checkFor live incidents, prove a model call succeeds after the policy/token change and that no token value appears in logs, UI, or sandbox config.
© vercel-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/firewall-ai-gateway-debug of vercel-labs/vercel-openclaw-archived.
Open the folder on GitHubat commit d592f7b
Compare with similar skills
Firewall AI Gateway 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Firewall AI Gateway Debug this skillvercel-labs/vercel-openclaw-archived | 117 | — | ~550 | Automated safety check: Pass | MIT | |
| Testingdoorkeeper-gem/doorkeeper | 5.5k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Vercel Advanced Troubleshootingjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Vercel Common Errorsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Replica DeployJakeschincariol/replica-skill | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Access Protected Vercel Deploymentvercel/vercel-plugin | 301 | — | ~1.9k | Automated safety check: Notes | Custom licence |
Similar skills
Vercel Advanced Troubleshooting
jeremylongshore/tons-of-skills-marketplace
Advanced debugging for hard-to-diagnose Vercel issues including cold starts, edge errors, and function tracing.
Vercel Common Errors
jeremylongshore/tons-of-skills-marketplace
Diagnose and fix common Vercel deployment and function errors.
Replica Deploy
Jakeschincariol/replica-skill
Ships an app clone live on the user's own domain: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, the…
- Official
Access Protected Vercel Deployment
vercel/vercel-plugin
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
Frontmcp Config
agentfront/frontmcp
A skill your agent uses when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options.
More from vercel-labs/vercel-openclaw-archived
All 16 skills in this repo- Official
Channel Debug Core
vercel-labs/vercel-openclaw-archived
Channel webhook triage for vercel-openclaw Slack/Telegram/Discord/WhatsApp issues: prove deployment state, collect admin readiness endpoints, build evidence-first handoff before fixes.
- Official
Lat Md
vercel-labs/vercel-openclaw-archived
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs.
- Official
Cron Watchdog Debug
vercel-labs/vercel-openclaw-archived
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.
- Official
Auth Store Debug
vercel-labs/vercel-openclaw-archived
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.
- Official
Gateway Proxy Debug
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.
- Official
Openclaw Bootstrap Debug
vercel-labs/vercel-openclaw-archived
OpenClaw bootstrap, bundle, config, and restore-asset debugging for vercel-openclaw: openclaw.bundle sidecars, plugin discovery, channel catalog, restart scripts, config hashes, dynamic resume…
Related
Works with
Categories
Questions about Firewall AI Gateway Debug
What does Firewall AI Gateway Debug do?
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…. Firewall AI Gateway Debug is an agent skill from vercel-labs/vercel-openclaw-archived, published by the product's own GitHub organization.update networkPolicy calls.
When should I use Firewall AI Gateway Debug?
Firewall AI Gateway Debug fits situations like: firewall policy application fails; tasks that involve OAuth and OpenID Connect; tasks that involve Debugging.
How do I install Firewall AI Gateway Debug in Claude Code?
Run `npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a claude-code`. Or copy the skill folder (.agents/skills/firewall-ai-gateway-debug in vercel-labs/vercel-openclaw-archived) into .claude/skills/firewall-ai-gateway-debug in your project. Claude Code loads it when a task matches its description.
How do I install Firewall AI Gateway Debug in Codex?
Run `npx skills add vercel-labs/vercel-openclaw-archived --skill firewall-ai-gateway-debug -a codex`. Or copy the skill folder (.agents/skills/firewall-ai-gateway-debug in vercel-labs/vercel-openclaw-archived) into .agents/skills/firewall-ai-gateway-debug in your project. Codex loads it when a task matches its description.
Can I use Firewall AI Gateway 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 firewall-ai-gateway-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/firewall-ai-gateway-debug, .gemini/skills/firewall-ai-gateway-debug, .github/skills/firewall-ai-gateway-debug and .opencode/skills/firewall-ai-gateway-debug in your project.
What does Firewall AI Gateway Debug need to run?
Going by SKILL.md and its folder, Firewall AI Gateway Debug needs the command-line tools its instructions call (node).
Does Firewall AI Gateway 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 Firewall AI Gateway 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 Firewall AI Gateway Debug use?
Firewall AI Gateway 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 Firewall AI Gateway Debug use?
About 550 tokens (SKILL.md is roughly 2.2k 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 Firewall AI Gateway Debug?
Skills that share tags, products or a category with Firewall AI Gateway Debug: Testing (doorkeeper-gem/doorkeeper, 5.5k stars), Vercel Advanced Troubleshooting (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Vercel Common Errors (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Replica Deploy (Jakeschincariol/replica-skill, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Firewall AI Gateway 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.