More screenshots
Works with the AI Agents you already use
Repair Resumable Upload Offset Bugs
Repair resumable-upload bugs where client/server offsets diverge, chunks are duplicated or skipped, expired sessions are reused, or completion accepts the wrong byte sequence.
$1
Repair Resumable Upload Offset Bugs
Example session with this skill installed
Our mobile client resumes from its last local offset after a timeout. The server may have committed that chunk already, so the retry can append it twice. Repair the protocol without changing allowed chunk sizes or storage provider.
- Read your context and instructions
- Compiled the repair resumable upload
The client offset is treated as authority even after ambiguous failures. The repair makes the server's committed offset/session generation authoritative, validates each chunk against that state, safely acknowledges exact retries, rejects conflicting ranges, and verifies final length/hash with tests around lost responses and concurrent resumes.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Resumable upload implementations often suffer from inconsistent offset tracking, race conditions during concurrent chunk writes, and leaking temporary files. Developers struggle to synchronize session identity, state ownership, and integrity checks across complex storage layers.
What it does
- Identifies and patches authoritative committed offset mismatches across repository components.
- Enforces strict chunk range validation to prevent data corruption during retries.
- Implements deterministic session generation and lease management for concurrent writers.
- Standardizes temporary file cleanup and session expiry logic without weakening security policies.
- Generates regression tests using local byte-range fixtures and loopback endpoints.
Frameworks & tools
Works with repository-level code using Read, Edit, and Bash tools. Applicable to any stack implementing chunked or resumable upload protocols.
Why this beats prompting it yourself
General prompts often miss the subtle race conditions and trust boundaries inherent in multi-part uploads. This skill follows a rigorous method to map state transitions and bind callbacks to the specific generations that created them, ensuring fixes don't just "look right" but handle edge cases like identical chunk retries and terminal failures correctly.
Use cases
- Fixing "offset mismatch" errors in S3-compatible or custom storage backends.
- Resolving data integrity issues caused by out-of-order chunk processing.
- Automating the cleanup of orphaned upload sessions and partial files.
- Adding redacted observability to upload pipelines without logging customer data.
Known limitations
Cannot interact with production services or live cloud environments. It focuses on local repository repairs and deterministic testing fixtures.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot redesign maximum size, chunk policy, storage layout, overwrite policy, authentication, retention, and public errors; cannot verify production infrastructure or prove every runtime, proxy, network, storage, clock, 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 patches and validation before merge. Keep production services, real credentials, customer payloads, and deployment out of scope.