reverse-skills-max: initial public release (restored, redacted, hardened)

reverse-skill-repo/CTF-Sandbox-Orchestrator/competition-queue-worker-drift/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: competition-queue-worker-drift
+description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-only behavior, follow retries or dead-letter handling, or connect an enqueued item to a later file, cache, email, or privilege-bearing side effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
+---
+
+# Competition Queue Worker Drift
+
+Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
+
+Use this skill when the decisive effect happens after enqueue, inside a worker, or only under async runtime state that differs from the request path.
+
+Reply in Simplified Chinese unless the user explicitly requests English.
+
+## Quick Start
+
+1. Map the async chain first: enqueue point, queue payload, worker consumer, retries, and final side effect.
+2. Keep request-time state separate from worker-time state.
+3. Record queue name, message shape, worker config, retry policy, and downstream store in one chain.
+4. Compare synchronous path and async path when behavior diverges.
+5. Reproduce the smallest enqueue-to-side-effect flow that proves the decisive async drift.
+
+## Workflow
+
+### 1. Map Enqueue And Worker Identity
+
+- Record queue names, topics, cron schedules, delayed jobs, dead-letter queues, worker processes, and consumer groups.
+- Note which config, env vars, feature flags, or credentials exist only in the worker environment.
+- Keep enqueue request, stored payload, and worker identity tied together.
+
+### 2. Trace Worker-Only State And Retries
+
+- Show how worker runtime differs from the request path: different env, files, mounts, caches, permissions, or clocks.
+- Record retry count, backoff, dedupe keys, failure handling, dead-letter flow, and idempotency behavior.
+- Distinguish immediate request success from eventual worker success or failure.
+
+### 3. Reduce To The Decisive Async Chain
+
+- Compress the result to the smallest sequence: enqueue -> worker runtime -> retry or branch -> resulting effect.
+- State clearly whether the decisive difference lives in payload shape, worker config, retry path, or downstream consumer.
+- If the issue is really about the file parser invoked by the worker, switch back to the tighter file-parser skill.
+
+## Read This Reference
+
+- Load `references/queue-worker-drift.md` for the queue checklist, retry checklist, and evidence packaging.
+
+## What To Preserve
+
+- Queue names, payloads, worker identities, retry metadata, dead-letter edges, and downstream effects
+- The exact worker-only config or state that changes behavior
+- One minimal enqueue-to-side-effect reproduction chain

reverse-skill-repo/CTF-Sandbox-Orchestrator/competition-queue-worker-drift/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Competition Queue Worker Drift"
+  short_description: "Trace queue payloads, worker state, retries, and async drift"
+  default_prompt: "After $ctf-sandbox-orchestrator is active, use $competition-queue-worker-drift to trace queued payloads, worker execution, retries, and the async state drift that creates the decisive behavior."
+
+policy:
+  allow_implicit_invocation: false

reverse-skill-repo/CTF-Sandbox-Orchestrator/competition-queue-worker-drift/references/queue-worker-drift.md

@@ -0,0 +1,27 @@
+# Queue Worker Drift Checklist
+
+## First Pass
+
+- Enqueue endpoint, queue or topic name, payload schema, worker process, schedule or delay, downstream store
+- Worker env, mounts, credentials, feature flags, config files, retry policy, dedupe behavior
+- Final effects: file write, cache mutation, email, report, artifact generation, privilege-bearing action
+
+## Async Chain To Reconstruct
+
+1. Request or cron enqueue occurs
+2. Payload stored or scheduled
+3. Worker picks it up under its own runtime state
+4. Retry, backoff, or failure path taken if relevant
+5. Side effect lands in file, DB, cache, email, or service
+
+## Evidence To Keep Together
+
+- Enqueue side: route, payload, queue name, task ID
+- Worker side: process, env, config, retry metadata, dedupe or lease state
+- Effect side: resulting artifact, downstream mutation, timestamps, and replay prerequisites
+
+## Common Pitfalls
+
+- Explaining only the request path and never proving the worker branch
+- Ignoring worker-only env or mount differences
+- Treating eventual side effects as synchronous behavior without isolating the async boundary