ClawHub

Golang Concurrency

v1.1.1

Golang concurrency patterns. Use when writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singl...

⭐ 0· 116·0 current·0 all-time
bySamuel Berthe@samber
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Go concurrency patterns, reviews, audits) match the declared needs: it only requires the 'go' binary and the ability to read project files; examples, references, and tests are all about concurrency patterns.
ℹ
Instruction Scope
SKILL.md directs the agent to write/review/audit code and to read repository files and diffs (expected). It also describes running audits with up to 5 parallel sub-agents and allows running tools like git, go, and linters — normal for this use case but worth noting because the agent will have capability to read and modify repository files and run build/test commands.
✓
Install Mechanism
Instruction-only skill with no install spec and no downloaded artifacts; nothing is written to disk by the skill itself beyond what the agent normally does.
✓
Credentials
No environment variables, secrets, or unrelated credentials are requested. The declared single binary requirement ('go') is appropriate for running tests, linters, or examples.
✓
Persistence & Privilege
always:false (not forced into every agent run). The skill permits autonomous invocation (disable-model-invocation:false) which is standard for skills; combined with allowed-tools this means the agent can run git/go/linter commands when invoked — expected for a code-review/write skill.
Assessment
This skill appears coherent for reviewing and writing concurrent Go code. Before installing, consider: (1) it can run commands (go, linters, git) and read/modify repository files — run it in a workspace you trust or a sandbox; (2) it does not request secrets or network endpoints, but git commands could use your configured credentials if the agent runs remote operations — restrict network/git access if unwanted; (3) verify the skill origin (homepage provided) if you need provenance; and (4) if you prefer human-only invocation, disable autonomous invocation or set the skill to user-invocable only.

Like a lobster shell, security has layers — review code before you run it.

latestvk971acb8v7ztp91wya57btaq8s83jyaz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

⚡ Clawdis
Binsgo

Comments