Skip to content
SkillModel-led502 tokens in use

competition-queue-worker-drift

A CTF sandbox workflow for tracing queues, async workers, retries and worker-only config from payload to side effect.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-queue-worker-drift
git clone https://github.com/zhaoxuya520/reverse-skill.git
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing competition-queue-worker-drift costs

123tokens idle
502tokens in use
744tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output15/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers