Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wshobson/go-concurrency-patterns
Master Go concurrency with goroutines, channels, sync primitives, and context.
Passed 20 of 22 test cases with the skill, and 20 of 22 without it.
1 fixed19 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We have an in-memory counter struct in Go where multiple goroutines concurrently increment a single integer `count` millions of times per second. No messages or work events are being passed. Should we build a channel multiplexer worker or use `sync.Mutex` / atomic operations?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends sync.Mutex or sync/atomic for updating an internal counter. | Passed | Passed |
| Acknowledges that shared memory primitives are appropriate when direct state locking is necessary. | Missed | Passed |
The instructions your model reads when the skill loads.
Production patterns for Go concurrency including goroutines, channels, synchronization primitives, and context management.
| Primitive | Purpose |
|---|---|
goroutine | Lightweight concurrent execution |
channel | Communication between goroutines |
select | Multiplex channel operations |
sync.Mutex | Mutual exclusion |
sync.WaitGroup | Wait for goroutines to complete |
context.Context | Cancellation and deadlines |
Don't communicate by sharing memory;
share memory by communicating.
package main
import (
"context"
test cases passed, vs 20 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.