Competition Race Condition State Drift

CommunityPopular

zhaoxuya520

competition-race-condition-state-drift

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 `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

Overview

Publisher	zhaoxuya520
Repository	`reverse-skill`
Skill name	`competition-race-condition-state-drift`
Stars	36.3K
Forks	5K
Bundled files	2
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by zhaoxuya520 on GitHub. Read the source before you install it.

Installation

Install the Competition Race Condition State Drift AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-race-condition-state-drift

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/zhaoxuya520/reverse-skill.git /tmp/reverse-skill
mkdir -p .claude/skills
cp -r /tmp/reverse-skill/CTF-Sandbox-Orchestrator/competition-race-condition-state-drift .claude/skills/competition-race-condition-state-drift

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Competition Race Condition State Drift in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Competition Race Condition State Drift on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Competition Race Condition State Drift is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Identify mutable state first: rows, cache keys, queue payloads, session fields, counters, or files.
Reproduce with smallest concurrent sequence and fixed timing assumptions.
Capture one baseline run and one racing run with only one variable changed.
Track read, check, write, enqueue, and commit boundaries separately.
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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Competition Race Condition State Drift AI skill do?

Why use Competition Race Condition State Drift on TypingMind?

Because you install it once and use it with any model. Competition Race Condition State Drift is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Competition Race Condition State Drift in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-race-condition-state-drift. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Competition Race Condition State Drift?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Competition Race Condition State Drift?

As many as you like. As long as a model supports skills, you can use Competition Race Condition State Drift with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Competition Race Condition State Drift AI skill free?

Yes. It is published on GitHub by zhaoxuya520 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Claude Handoff

mattpocock

CommunityPopular

Hand the current conversation off to a fresh background agent that picks up the work immediately.

Finishing A Development Branch

obra

CommunityPopular

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Receiving Code Review

obra

CommunityPopular

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative…

Requesting Code Review

obra

CommunityPopular

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Competition Race Condition State Drift

Quick Start

Workflow

1. Map Mutable Boundaries

2. Reproduce Timing Window

3. Reduce To Decisive Race Chain

Read This Reference

What To Preserve

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now