This skill is a downstream specialization of the ctf-sandbox-orchestrator skill. It covers challenges where the decisive effect happens after enqueue, inside a worker, or under runtime state that differs from the request path.
The agent maps queue names, payload shape, worker identity, retry and dead-letter behavior and the downstream effect, then reduces the result to the smallest enqueue-to-side-effect chain. Replies are in Simplified Chinese unless English is requested.
What You Get
- A method that keeps request-time state apart from worker-time state
- A checklist for queue names, payload schema, worker environment, mounts and retry policy
- An async chain template: enqueue, stored payload, worker pickup, retry or branch, side effect
- A hand-off rule to the file parser skill when the worker’s parser is the real issue
Common Use Cases
- Explaining why a worker behaves differently from the web request path in a lab
- Following retries and dead-letter handling for a queued job in a CTF
- Linking an enqueued item to a later file, cache or email effect
What Makes It Unique
It treats the async boundary as the object of study and asks for proof of the worker branch, not just the request path. It names whether the difference lives in payload shape, worker config, retry path or downstream consumer, and it runs only after the orchestrator skill has set sandbox assumptions.
Under The Hood
The skill is instruction text only: a SKILL.md, one reference checklist and an agent config file that disables implicit invocation. It ships no scripts and does not itself fetch pages, call APIs, run commands or write files. The agent inspects the sandbox with whatever tools the user already provides.