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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and token-efficient with a clean single-reference progressive-disclosure structure and clear sequencing. Its main weakness is actionability: it describes a methodology with verification concepts but provides no executable code, commands, or worked replay example, and lacks an explicit error-recovery feedback loop.

Suggestions

Add one minimal worked example of a racing sequence (e.g., two concurrent requests with a concrete read-check-write gap and the resulting drift) to lift actionability from methodology to executable.

Insert an explicit validation checkpoint and feedback loop, such as 'if the race run does not reproduce drift, isolate the single variable that flips ordering and re-run' before declaring the root cause.

Tighten the opening paragraph to avoid re-stating the `$ctf-sandbox-orchestrator` gating already present in the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanation Claude already knows; sections (Quick Start, Workflow, Read This Reference, What To Preserve) each earn their place. Minor redundancy of the parent-gating instruction (already in the frontmatter) keeps this at the top anchor.	3 / 3
Actionability	Guidance is specific (track 'read, check, write, enqueue, and commit boundaries separately'; compress to 'request A and B ordering -> stale check or lock gap -> conflicting writes') but stays at the methodology level with no executable code, commands, or worked replay examples.	2 / 3
Workflow Clarity	A clear 5-step Quick Start and 3-step Workflow are sequenced and include verification ('Prove final state drift from a clean reset', parity checks), but there is no explicit validate->fix->retry feedback loop, which the rubric requires for a 3.	2 / 3
Progressive Disclosure	A single well-signaled one-level-deep reference ('Load references/race-condition-state-drift.md for race harness ideas, evidence blocks, and parity checks') points to a real file, and the body is cleanly sectioned for navigation.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it concisely states the skill's niche, lists concrete failure modes, provides explicit 'Use when' triggers, and is gated to a parent orchestrator to avoid mis-routing. Voice is appropriately third person with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and scenarios ('reproduce timing-sensitive bugs, concurrent state corruption, duplicate actions, stale reads, or privilege or balance drift') rather than vague language, matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('CTF-sandbox workflow for race windows, ordering bugs, idempotency failures...') and when with explicit 'Use when...' triggers, satisfying the top anchor.	3 / 3
Trigger Term Quality	The 'Use when the user asks to reproduce timing-sensitive bugs, concurrent state corruption, duplicate actions, stale reads...' clause gives natural phrasings a user would actually say, providing good coverage of trigger terms.	3 / 3
Distinctiveness Conflict Risk	A clear niche (race-condition state drift in a CTF sandbox) with distinct triggers and an explicit gate to use only after `$ctf-sandbox-orchestrator`, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zhaoxuya520/reverse-skill
Path: CTF-Sandbox-Orchestrator/competition-race-condition-state-drift/SKILL.md
Commit: 6aa1362

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.