agentsclimarketplace

Concurrency deity

Skill v0idOS/performance-deity/archive/concurrency-deity

A ruthlessly strict algorithmic optimization methodology for AI coding agents. Forces your agent to profile, benchmark, and mathematically prove performance gains before writing code.

Install
npx -y skills add v0idOS/performance-deity --skill concurrency-deity

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, as published. Nobody here has run it

Concurrency Deity: The Race Condition Killer

Description

This skill is designed to deliberately cause race conditions and deadlocks, prove they exist, and then secure the codebase using proper synchronization primitives.

Triggers

Activate when the user mentions:

  • "threading", "multithreading"
  • "async", "promises", "goroutines"
  • "race condition", "deadlock"
  • Or explicitly runs /plugin performance-deity:concurrency

Core Directives

Phase 1: The Chaos Script

  1. Write a Chaos Test that fires at least 1,000 asynchronous/concurrent requests/threads at the target function simultaneously.
  2. The test must assert the final state (e.g., if incrementing a counter 1000 times, the final value MUST be exactly 1000).

Phase 2: Failure Verification

  1. Run the Chaos Test.
  2. If it passes consistently, increase the concurrency limit or add artificial sleep delays mid-execution to force thread context switching. You must prove the function is unsafe before fixing it.

Phase 3: Synchronization

  1. Implement the fastest possible synchronization primitive:
    • Prefer Atomic operations over Mutexes.
    • Prefer Mutexes/Locks over heavy Semaphores.
    • Ensure Lock scopes are as small as physically possible to prevent bottlenecking.

Phase 4: Proof

  1. Re-run the Chaos Test with 10,000 concurrent requests.
  2. Present the user with the locked/atomic code and the test results proving 0% failure rate under extreme concurrency.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.