Skip to content

Competition Queue Worker Drift

Traces queue payloads, async workers, retries and worker-only config drift in CTF sandbox work

Stars
43,969
Licence
MIT
Files
3 files

What it does

This is a specialist skill for an internal CTF (capture-the-flag security competition) sandbox workflow. When active, it guides the agent to follow a task from the moment something is put onto a queue, through the background worker that processes it, to the final effect such as a file write, cache change, email, or privilege change. It asks the agent to record queue names, payload shapes, retry and dead-letter behavior, and any settings that exist only in the worker environment, and to reduce the findings to one minimal reproduction chain. It is written as a downstream add-on that should only run after a parent skill, ctf-sandbox-orchestrator, has already set the sandbox assumptions, and replies in Simplified Chinese by default.

Great for

  • Security students or competitors working on CTF challenges that involve background jobs or message queues
  • Researchers analysing how asynchronous workers behave differently from request-time code in a lab sandbox
  • Developers debugging why a queued job behaves differently from the same action run synchronously

Skip it if

  • Production systems or real third-party infrastructure: the skill is aimed at sandboxed competition targets, and tracing privilege-bearing effects on systems you do not own could be unauthorised access
  • Anyone who has not installed the parent ctf-sandbox-orchestrator skill: the skill tells the agent to return to that parent first, so it will not work on its own as described
  • General queue debugging unrelated to security analysis, where a standard logging or tracing guide would be simpler

Try asking

  • “Trace the queue payload for this CTF challenge from the enqueue endpoint to the worker that writes the uploaded file”
  • “Explain why the retry worker in this sandbox performs a privileged action that the request path does not”
  • “Map the cron jobs and dead-letter queue in this lab target and show the smallest enqueue-to-side-effect chain”
Step-by-step guide: how to use Competition Queue Worker DriftInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 3 original files, the MIT licence and an attribution note.

    competition-queue-worker-drift.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip competition-queue-worker-drift.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip competition-queue-worker-drift.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Install and activate ctf-sandbox-orchestrator first, since this skill is designed to be routed to from it and says to return there if sandbox assumptions are missing
  • Only use it against sandboxed competition targets you are authorised to test, and keep to the evidence-recording workflow it describes
  • Provide the enqueue code, a sample payload and the worker config so the agent can follow the chain instead of guessing

What's inside

  • agents/openai.yaml
  • references/queue-worker-drift.md
  • SKILL.md

Redistributed unmodified from zhaoxuya520/reverse-skill under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.