competition-request-normalization-smuggling — Claude Code skill
competition-request-normalization-smuggling is a Claude Code skill that analyzes HTTP parsing discrepancies between proxies and backend servers in CTF workflows.
MIT 110 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -a claude-codeWhat competition-request-normalization-smuggling does
The skill runs as a downstream workflow after $ctf-sandbox-orchestrator establishes the sandbox environment. It maps parsing hops, records header canonicalization and path normalization, and isolates differential request behavior across proxies and backend layers.
It requires the reference file references/request-normalization-smuggling.md for the parser-differential checklist. The output defaults to Simplified Chinese unless requested otherwise.
What it helps with
- map HTTP parsing hops across proxy and backend
- record path normalization and header canonicalization
- build differential request pairs
- isolate routing and framing discrepancies
Example prompts for the agent
- Trace the parsing differences between the proxy and the backend
- Analyze Host header ambiguity and path decoding drift
- Build a differential request chain to test route divergence
How to install competition-request-normalization-smuggling
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -a claude-code2Manually: put the files in place
~/.claude/skills/competition-request-normalization-smuggling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-request-normalization-smuggling/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -a codex2Manually: put the files in place
.agents/skills/competition-request-normalization-smuggling/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -a cursor2Manually: put the files in place
.cursor/skills/competition-request-normalization-smuggling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-request-normalization-smuggling/SKILL.md2Manually: put the files in place
.github/skills/competition-request-normalization-smuggling/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-request-normalization-smugglingManually: put the files in place
.devin/skills/competition-request-normalization-smuggling/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -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-request-normalization-smuggling
How to install competition-request-normalization-smuggling in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling -a claude-code in your terminal and reference ~/.claude/skills/competition-request-normalization-smuggling/SKILL.md.
What does competition-request-normalization-smuggling do?
It automates the analysis of parser differentials and HTTP normalization gaps across different routing hops in CTF environments.
What is required to run competition-request-normalization-smuggling?
The $ctf-sandbox-orchestrator must be active first, and the reference file references/request-normalization-smuggling.md must be loaded.
Source text
SKILL.md · MIT
--- name: competition-request-normalization-smuggling description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for parser differentials, HTTP normalization gaps, ambiguous headers, path decoding drift, transfer-framing mismatches, and request smuggling routes. Use when the user asks to trace proxy and backend parse differences, conflicting path normalization, Host or forwarded-header ambiguity, CL/TE issues, or routing outcomes that differ across hops. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Request Normalization Smuggling 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 request interpretation changes between proxy, middleware, and backend parser layers. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Map every parsing hop: client-facing proxy, gateway, app server, and downstream service. 2. Record path normalization, header canonicalization, transfer framing, and host derivation at each hop. 3. Capture one accepted baseline request and one differential request with minimal delta. 4. Prove which hop interprets the request differently. 5. Reproduce one minimal differential path that yields decisive behavior. ## Workflow ### 1. Map Parse And Routing Boundaries - Record `Host`, forwarded headers, path decoding, slash collapsing, dot-segment handling, and case behavior. - Note `Content-Length`, `Transfer-Encoding`, chunk framing, and connection reuse behavior when relevant. - Keep edge parser and backend parser decisions side by side. ### 2. Prove Differential Interpretation - Build paired requests that differ in one canonicalization dimension only. - Capture proxy logs, backend logs, route match, and downstream request shape. - Show where route, auth scope, or body boundary diverges. ### 3. Reduce To Decisive Smuggling Chain - Compress to: crafted request -> parser differential across hops -> unintended routed request or hidden endpoint reach -> resulting effect. - State whether root cause is path normalization drift, header ambiguity, transfer framing differential, or host-derivation confusion. - If the chain becomes primarily runtime routing without framing tricks, hand off to runtime routing skill. ## Read This Reference - Load `references/request-normalization-smuggling.md` for parse-differential checklist and evidence packaging. ## What To Preserve - Raw request pairs, hop-by-hop interpretation, and final routed target - Exact normalization or framing delta that flips behavior - One minimal replayable differential request path
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill