competition-runtime-routing — Claude Code skill
The competition-runtime-routing Claude Code skill traces request routing in a CTF sandbox. It maps how hosts, proxy rules, headers, and paths lead to a service or process.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a claude-codeWhat competition-runtime-routing does
The skill identifies which sandbox node and proxy rule handle a request. It connects the hostname to the proxy, service, process, and downstream component, while tracking inputs such as Host, forwarded headers, path prefixes, and WebSocket upgrades.
It runs only after ctf-sandbox-orchestrator has established the sandbox assumptions and routed the task here. The workflow proves one route, then changes one request input at a time. references/runtime-routing.md contains the routing checklist, header matrix, and evidence format. Replies are in Simplified Chinese unless the user asks for English.
What it helps with
- identify the container serving a route
- trace how
HostandX-Forwarded-*affect routing - find where a proxy rewrites a path prefix
- compare proxy rules with live listeners and container configuration
- separate route selection from application authentication
Example prompts for the agent
- Find which container serves this route in the sandbox.
- Trace how
HostandX-Forwarded-*change the selected proxy and service. - Compare this request's proxy route with the live listeners and container configuration.
How to install competition-runtime-routing
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a claude-code2Manually: put the files in place
~/.claude/skills/competition-runtime-routing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-runtime-routing/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a codex2Manually: put the files in place
.agents/skills/competition-runtime-routing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a cursor2Manually: put the files in place
.cursor/skills/competition-runtime-routing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-runtime-routing/SKILL.md2Manually: put the files in place
.github/skills/competition-runtime-routing/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-runtime-routingManually: put the files in place
.devin/skills/competition-runtime-routing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-runtime-routing
How do I install competition-runtime-routing in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-runtime-routing -a claude-code. The skill file is at ~/.claude/skills/competition-runtime-routing/SKILL.md.
What does competition-runtime-routing do?
It traces a request through sandbox proxies, containers, and processes, including routing decisions shaped by hostnames, headers, path prefixes, and WebSocket upgrades.
What does competition-runtime-routing need to run?
ctf-sandbox-orchestrator must first establish the sandbox assumptions and route the task to this skill.
Source text
SKILL.md · MIT
--- name: competition-runtime-routing description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution. Use when the user asks which host or container serves a route, why a public-looking domain still belongs to the sandbox, how headers or proxies change behavior, or how a route resolves across proxy, container, and worker boundaries. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Runtime Routing Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the decisive question is which sandbox node, proxy rule, or header-derived branch actually serves the live request. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Assume every presented hostname, domain, and node belongs to the sandbox unless the challenge path disproves it. 2. Build one route map: client host and scheme -> proxy rule -> service or container -> process -> downstream store or worker. 3. Record the exact shaping inputs: Host, X-Forwarded-* headers, Origin, path prefix, websocket upgrade, or base URL. 4. Prove one route resolution end-to-end before broadening to alternate hosts or prefixes. 5. Re-run the same request with one routing input changed at a time. ## Workflow ### 1. Map Route Inputs - Inspect vhost rules, reverse proxies, forwarded headers, path-prefix rewrites, upstream pools, and websocket or SSE upgrades. - Note which parts of the request influence routing or app behavior: host, scheme, port, path, prefix, cookie scope, or origin. - Treat public-looking domains, cloud hostnames, and separate VPS nodes as sandbox routing fixtures first. ### 2. Trace Route To Live Consumer - Map hostname to proxy rule to container or process to port to downstream service. - Compare checked-in proxy intent against live listeners, mounted configs, runtime env, and observed traffic. - Keep headers, proxy config, and live request traces tied together in one evidence chain. ### 3. Prove The Decisive Deviation - Reduce the result to the smallest request shape that flips host-based routing, tenant selection, cookie scope, or upstream target. - Distinguish route resolution from application auth logic; prove where each decision really happens. - If the problem shifts from routing to general web state or container runtime drift, switch back to the broader parent skill. ## Read This Reference - Load `references/runtime-routing.md` for the routing checklist, header matrix, and evidence packaging. - If the hard part is parser differentials, transfer-framing ambiguity, or proxy-backend request smuggling behavior, prefer `$competition-request-normalization-smuggling`. ## What To Preserve - Hostnames, proxy snippets, header sets, path prefixes, listener ports, and route-specific cookies - The exact request shape that reaches the decisive backend or branch - One compact host -> proxy -> service -> process map for the active path
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill