- Home
- Skills
- APIs & Backend
- Repair Range Request Corruption
Works with the AI Agents you already use
Repair Range Request Corruption
Repair HTTP byte-range bugs that return wrong offsets, corrupt resumable downloads, mishandle suffix or open-ended ranges, combine incompatible validators, or emit invalid 206/416 responses.
$1
Repair Range Request Corruption
Example session with this skill installed
Repair our Go download handler. A resumed request bytes=1048576- starts one byte late, suffix ranges fail on small files, and If-Range is checked after opening the partial stream. Use local byte fixtures. Preserve authorization, storage abstraction, ETag policy, compression, retries, and errors.
- Read your context and instructions
- Compiled the repair range request
Range-contract defect found. The parser converts inclusive HTTP bounds into half-open storage offsets twice, causing an off-by-one resume gap, and suffix handling underflows below zero. The repair creates one canonical interval conversion, checks If-Range before partial delivery, preserves authorization/storage/compression/retry policy, and verifies 200, 206, 416, suffix, open-ended, multipart, and changed-validator cases byte for byte.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Resumable downloads fail when byte offsets are off-by-one or range headers disagree with the actual payload. These bugs are notoriously difficult to debug, often resulting in corrupted files, duplicated data, or incorrect 206 Partial Content responses.
What it does
- Analyzes
RangeandContent-Rangeparsing logic to identify inclusive interval math errors. - Fixes suffix, open-ended, and multipart range calculations that lead to boundary byte corruption.
- Ensures
If-Rangevalidators correctly prevent serving stale bytes from modified representations. - Standardizes response framing to align headers with actual payload lengths.
- Generates deterministic local fixtures to reproduce and verify fixes without production access.
Why this beats prompting it yourself
General LLMs often struggle with the precise 0-indexed vs 1-indexed math required for HTTP range requests and frequently suggest "fixes" that break multipart compliance. This skill enforces a strict ownership and normalization register, ensuring that authorization and cache policies remain untouched while the underlying byte math is repaired.
Use cases
- Fixing corrupted file downloads where the first or last bytes are missing.
- Correcting 416 Requested Range Not Satisfiable errors on valid files.
- Repairing multipart range responses where boundaries are incorrectly merged.
- Synchronizing compressed offsets with uncompressed file bounds.
Known limitations
Does not modify authorization logic, storage drivers, or external retry policies. Requires local repository files to function and cannot test against live production endpoints.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Cannot choose or change authorization, storage reads, cache policy, validators, compression policy, retry/resume rules, and public errors; cannot verify production infrastructure or prove every runtime, proxy, network, or scheduler ordering.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
Run on a clean branch with repository files and disposable local fixtures. Review every patch and validation result before merge. Keep production services, real credentials, customer payloads, and deployment out of scope.