Skip to content
alyn
zhaoxuya520

Competition Race Condition State Drift skill

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for race windows, ordering bugs, idempotency failures, lock gaps, concurrent worker drift, and state inconsistencies that produce decisive effects. Use when the user asks to reproduce timing-sensitive bugs, concurrent state corruption, duplicate actions, stale reads, or privilege or balance drift caused by request ordering. Use only after `$

$npx skills add zhaoxuya520/reverse-skill --skill competition-race-condition-state-drift
View this skill on GitHubzhaoxuya520/reverse-skill/CTF-Sandbox-Orchestrator/competition-race-condition-state-drift/SKILL.md
Pack stars
44,428
Pack installs
64k
Alyn Score
71/99
Updated
2 months ago
License
MIT
– views – installs via Alyn

Install Competition Race Condition State Drift

Pick your agent. Every command is ready to paste.

$npx skills add zhaoxuya520/reverse-skill --skill competition-race-condition-state-drift

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads competition-race-condition-state-drift when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the competition-race-condition-state-drift skill”. In Codex, type $competition-race-condition-state-drift.

The skill itself

SKILL.md

FolderGitHub

Competition Race Condition State 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 behavior depends on request timing, async ordering, lock gaps, or stale state.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Identify mutable state first: rows, cache keys, queue payloads, session fields, counters, or files.
  2. Reproduce with smallest concurrent sequence and fixed timing assumptions.
  3. Capture one baseline run and one racing run with only one variable changed.
  4. Track read, check, write, enqueue, and commit boundaries separately.
  5. Prove final state drift from a clean reset.

Workflow

1. Map Mutable Boundaries

  • Record transaction scope, lock behavior, retry logic, idempotency keys, cache invalidation, and queue handoff.
  • Note where read-check-write is split across requests, workers, or services.
  • Keep each boundary tied to exact timestamps or sequence numbers.

2. Reproduce Timing Window

  • Build deterministic concurrent inputs with controlled delay, duplicate requests, or reordered worker execution.
  • Compare accepted and rejected paths under identical payloads.
  • Record which condition flips when ordering changes.

3. Reduce To Decisive Race Chain

  • Compress to: request A and B ordering -> stale check or lock gap -> conflicting writes -> resulting capability or artifact.
  • State whether root cause is missing lock, weak idempotency, stale cache read, delayed async commit, or retry side effect.
  • If the path becomes queue-dominant, hand off to queue worker drift skill.

Read This Reference

  • Load references/race-condition-state-drift.md for race harness ideas, evidence blocks, and parity checks.

What To Preserve

  • Mutable keys, transaction boundaries, lock behavior, and idempotency markers
  • Timestamped or sequenced traces for baseline and race runs
  • One minimal replayable concurrent sequence proving drift

Tips for Competition Race Condition State Drift

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It bundles reference files. The agent reads them only when needed, so they cost no context until then.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Competition Race Condition State Drift

What does the Competition Race Condition State Drift skill do?

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for race windows, ordering bugs, idempotency failures, lock gaps, concurrent worker drift, and state inconsistencies that produce decisive effects. Use when the user asks to reproduce timing-sensitive bugs, concurrent state corruption, duplicate actions, stale reads, or privilege or balance drift caused by request ordering. Use only after `$

How do I install Competition Race Condition State Drift?

Run "npx skills add zhaoxuya520/reverse-skill --skill competition-race-condition-state-drift" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Competition Race Condition State Drift work in Cursor and Codex?

Yes. Competition Race Condition State Drift uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Competition Race Condition State Drift free?

Competition Race Condition State Drift is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Competition Race Condition State Drift?

Competition Race Condition State Drift is published by zhaoxuya520 in the zhaoxuya520/reverse-skill repository, together with 29 other skills.

Similar skills. From other creators.