sota-async-concurrency SKILL.md skillA
sota-async-concurrency from martinholovsky/sota-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinholovsky/sota-skills/sota-async-concurrency@git:20261012.ae1b29bPins git:20261012.ae1b29b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinholovsky/sota-skills
- Path
skills/sota-async-concurrency/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261012.ae1b29b, committed Oct 12, 2026
- First version recorded
- Jun 17, 2026
- Size
- 8,962 bytes
- Repository stars
- 23
- License
- CC-BY-4.0
State-of-the-art rules for writing and auditing asynchronous and concurrent code across runtimes (Python asyncio, JS/Node, Go, Rust, JVM). Use when building anything with async/await, threads, processes, event loops, task groups, channels, or queues — and when auditing existing code for race conditions, deadlocks, leaked tasks, blocked event loops, missing cancellation, or backpressure failures. Not for latency/throughput profiling and optimization — use sota-performance. Trigger keywords…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SOTA Async & Concurrency ## Purpose Concurrency bugs are the most expensive class of defect: they pass tests, ship, and then corrupt data or hang production under load. This skill encodes the 2026 state of the art for concurrent design and the bug catalog auditors need to spot defects **by reading code**, without reproducing them. Concepts are cross-language; per-runtime notes are inlined where semantics genuinely differ (GIL, goroutine scheduling, tokio executors, Node's single loop). Two operating modes. Pick one explicitly before starting. ## BUILD mode When writing new concurrent code: 1. **Classify the workload first.** I/O-bound → async/event loop. CPU-bound → threads (if runtime has real parallelism) or processes. Mixed → async front-end + bounded worker pool. Read [`rules/01`](rules/01-models-and-structure.md) before choosing. 2. **Structured concurrency is the default.** Every task lives inside a scope (TaskGroup / nursery / errgroup / JoinSet) that joins or cancels it. Spawning a task with no owner is a design smell requiring written justification. 3. **Bound everything.** Every queue, channel, connection pool, in-flight …
Read the whole file at its exact version.
How to install
mdr add martinholovsky/sota-skills/sota-async-concurrency@sha256:0de40815a56a8be3The line at the top of this page pins the label git:20261012.ae1b29b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_h7pqbyu2jyu7qdf5)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 17, 2026 and Oct 12, 2026, about one every 39 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.ae1b29b latest | 2026-10-12 | ae1b29b | 8,962 B | A | view · diff |
| git:20260916.296902d | 2026-09-16 | 296902d | 8,610 B | A | view · diff |
| git:20260716.e4afc80 | 2026-07-16 | e4afc80 | 8,208 B | A | view · diff |
| git:20260617.c5d2c7b | 2026-06-17 | c5d2c7b | 8,126 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8962 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
martinholovsky/sota-skills · 23 stars · license CC-BY-4.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h7pqbyu2jyu7qdf5 GET https://markdownregistry.com/api/v1/resolve?ref=martinholovsky/sota-skills/sota-async-concurrency GET https://markdownregistry.com/api/v1/blob/0de40815a56a8be36e70c6859658c613dc1169eee9f9888923a6073764e1a3fb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.