What problem does it solve? Front-end proxies, CDNs, and load balancers often disagree with origin servers on where one HTTP request ends and the next begins. This Skill provides a structured playbook for detecting and exploiting these message-boundary disagreements (CL.TE, TE.CL, TE.TE, H2.CL, H2.TE, CL.0) during authorized penetration tests and CTF challenges. ## Core Features & Use Cases - Classic Desync Probes: Byte-exact CL.TE and TE.CL payloads with chunk-length calculation guidance, plus 8 Transfer-Encoding obfuscation variants for TE.TE parser differentials. - HTTP/2 Smuggling: H2.CL and H2.TE downgrade attacks, pseudo-header confusion, and CL.0 connection-close desync with detection procedures. - Impact Escalation: Chains smuggling into cache poisoning, queue poisoning, and client-side desync via browser fetch pipelines, with a CDN/reverse-proxy behavior matrix (HAProxy, Nginx, Cloudflare, AWS ALB, Envoy, and more). - Use Case: During an authorized assessment of a site behind Cloudflare, use the detection decision tree to identify the front/back TE preference, confirm a CL.TE desync with a timing probe, then escalate to cache poisoning of a static asset. ## Quick Start Ask the agent to test the target for HTTP request smuggling using the CL.TE and TE.CL probes from this skill and confirm any desync with a timing-based follow-up request.