Skip to content

hgxszhj/https-github.com-zhaoxuya520-reverse-skill / CTF-Sandbox-Orchestrator/competition-queue-worker-drift

competition-queue-worker-drift

Unverified

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.

FileKindSize
SKILL.mdskill md3.0 KB
agents/openai.yamlconfig402 B
references/queue-worker-drift.mdmarkdown1.1 KB

references/queue-worker-drift.md

View on GitHub
# 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
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall