Go Concurrency
Goroutine lifecycle, channels, mutexes, errgroup, worker pools, fan-out/fan-in — every goroutine a liability until proven necessary
- What
- Goroutine lifecycle, channels, mutexes, errgroup, worker pools, fan-out/fan-in — every goroutine a liability until proven necessary
- Cost
- Free
- Needs
- a Go project (the go toolchain)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Go concurrency skill with a blunt persona: every goroutine is a liability until proven necessary — correctness and leak-freedom come before performance. It covers goroutine lifecycle and leak prevention, channels and select, channel ownership and direction, sync primitives (Mutex, RWMutex, sync.Map, sync.Once, atomics), errgroup, singleflight, worker pools, and fan-out/fan-in pipelines — with write mode (implement), review mode (PR diffs: leaks, missing context propagation, ownership violations), and audit mode (up to 5 parallel sub-agents over a codebase). Distinct from the already-published samber skills — it explicitly defers non-concurrency defensive bugs to golang-safety and post-mortem debugging of hung/racing programs to golang-troubleshooting. By @samber, listed here with credit to its creator. Honest caveats: concurrency guidance can't save you from a design that didn't need concurrency in the first place — the skill's first instinct is to question the goroutine, which is right and occasionally annoying. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project (the go toolchain) Install "Go Concurrency" for me. Goroutine lifecycle, channels, mutexes, errgroup, worker pools, fan-out/fan-in — every goroutine a liability until proven necessary Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-concurrency/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-concurrency skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-concurrency". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.