CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/race-condition-test-author

Build deterministic race-condition tests - identify shared mutable state, drive interleavings via barriers / latches / manual scheduling; use ThreadSanitizer (clang `-fsanitize=thread`) for C/C++ data race detection; run the Go race detector end-to-end (`go test -race`, GORACE tuning, `-count`/`-cpu` stress, goroutine-leak gating with go.uber.org/goleak - references/go.md); use jcstress (`@JCStressTest` + `@Actor` + `@Outcome`) for JVM stress; use Loom virtual-thread interleavings for parallel testing. Use when a defect only reproduces under load on shared in-process state (cache, counter, connection pool, lazy-init singleton), when writing the regression test for a race-condition incident before the fix lands, or when adding `-race` to a Go CI matrix.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

82%Weight 40%Scale 1-5

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

A well-sequenced, highly actionable multi-language race-condition testing skill with real reference files and an anti-patterns safety net. It is dense and mostly efficient, with only minor conciseness and organization gaps that keep it just short of top marks.

Suggestions

Trim restated-common-knowledge asides (the opening 'works on my machine' framing and the JMM/volatile and M:N-scheduling explanations) to tighten conciseness toward a 5.

Make the test-authoring feedback loop explicit inside the steps (run -> if race detected, fix and re-run; if green but flaky, switch to -count/-cpu or sanitizers) rather than only surfacing it in the Anti-patterns table.

Consider offloading the jcstress and Loom deep-dives into reference files (mirroring references/go.md) so SKILL.md reads as an overview with consistently one-level-deep references.

DimensionReasoningScore

Conciseness

The body is dense and code-forward, but a few asides restate concepts Claude already knows - e.g. 'Race conditions are the canonical works on my machine, breaks under load bug' and 'Virtual threads run M:N on OS threads' / 'reordering allowed under JMM unless volatile or final' - which are minor over-explanation that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready examples across Python (barrier test, Hypothesis), bash (clang -fsanitize=thread, go test -race, jcstress jar), Java (jcstress @JCStressTest, Loom virtual-thread executor), and YAML CI snippets covering the common cases.

5 / 5

Workflow Clarity

A clear Step 1-7 sequence (identify state -> deterministic interleaving -> TSan -> jcstress -> Loom -> property-based -> CI) with a Step 1 checklist and an anti-patterns table supplying feedback guidance, but explicit validate->fix->retry checkpoints within steps are only implied via the anti-patterns rather than stated inline.

4 / 5

Progressive Disclosure

Good structure with a well-signaled one-level-deep reference (the full Go workflow in references/go.md, which itself links to goleak-filter-options.md - both verified present), but the detailed TSan/jcstress/Loom sections remain inlined in SKILL.md while only Go is offloaded, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

A strong, third-person description that pairs a comprehensive list of concrete capabilities with an explicit, multi-clause 'Use when...' trigger. It is long but every clause carries specifics rather than fluff, so verbosity does not erode the scored dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across stacks - 'identify shared mutable state', 'drive interleavings via barriers / latches / manual scheduling', ThreadSanitizer for C/C++, Go race detector with GORACE/-count/-cpu/goleak, jcstress, and Loom virtual threads - giving comprehensive coverage rather than vague claims.

5 / 5

Completeness

Explicitly answers both what ('Build deterministic race-condition tests...') and when ('Use when a defect only reproduces under load on shared in-process state... when writing the regression test for a race-condition incident before the fix lands, or when adding -race to a Go CI matrix') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural practitioner terms including synonyms ('race-condition', 'data race', 'race detector', '-race') plus concrete trigger objects ('cache, counter, connection pool, lazy-init singleton') and 'Go CI matrix', matching the comprehensive-synonym anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (deterministic race-condition test authoring) anchored by named tools (TSan, jcstress, goleak, Loom) and specific triggers, making conflict with sibling skills like deadlock-detection-harness or async-ordering-tests minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents