golang-concurrency
Golang concurrency patterns. Use when writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Also triggers when you detect goroutine leaks, race conditions, channel ownership issues, or need to choose between channels and mutexes.
86
81%
Does it follow best practices?
Impact
98%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (Go concurrency patterns), lists specific concrete capabilities and concepts, and provides comprehensive trigger guidance. It uses third person voice appropriately and includes both proactive triggers (writing/reviewing) and reactive triggers (detecting issues). The rich set of Go-specific terminology makes it highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, fan-out/fan-in pipelines, goroutine leaks, race conditions, channel ownership issues, and choosing between channels and mutexes. | 3 / 3 |
Completeness | Clearly answers both 'what' (Golang concurrency patterns, writing/reviewing concurrent Go code) and 'when' with an explicit 'Use when...' clause covering multiple trigger scenarios including writing, reviewing, detecting issues, and making design decisions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would use: 'goroutines', 'channels', 'select', 'locks', 'sync primitives', 'errgroup', 'singleflight', 'worker pools', 'fan-out/fan-in', 'goroutine leaks', 'race conditions', 'concurrent Go code'. These are exactly the terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Go concurrency specifically, with domain-specific triggers like 'goroutines', 'channels', 'errgroup', 'singleflight' that are unlikely to conflict with general Go skills or concurrency skills in other languages. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured concurrency skill with strong organizational patterns (tables, checklists, clear modes) and good progressive disclosure intent through references to supporting files. Its main weaknesses are the lack of executable code examples in the body (deferred to reference files that aren't provided) and some unnecessary explanatory prose. The decision tables and common mistakes section provide high-value, actionable guidance.
Suggestions
Add at least 2-3 inline executable code examples for the most critical patterns (e.g., proper goroutine shutdown with context, errgroup usage) rather than deferring all code to reference files.
Trim the introductory paragraph ('Go's concurrency model is built on goroutines and channels...') — Claude already knows this; jump straight to the principles.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and checklists, but includes some unnecessary explanatory text that Claude already knows (e.g., 'Go's concurrency model is built on goroutines and channels. Goroutines are cheap but not free'). The persona and modes section adds some overhead. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | The skill provides concrete guidance through decision tables, checklists, and specific tool references (errgroup.SetLimit, goleak, -race flag), but lacks executable code examples in the main body. Code examples are deferred to reference files. The common mistakes table is actionable but would benefit from inline code snippets showing the fix patterns. | 2 / 3 |
Workflow Clarity | The three modes (Write, Review, Audit) are clearly defined with distinct workflows. The concurrency checklist provides an explicit pre-flight validation sequence. The audit mode specifies a clear 5-step parallel process. The checklist format serves as a validation checkpoint before spawning goroutines. | 3 / 3 |
Progressive Disclosure | The skill references multiple external files (references/channels-and-select.md, references/sync-primitives.md, references/pipelines.md) and cross-references other skills, which is good structure. However, no bundle files were provided, so these references are unverifiable. The main body contains substantial inline content (three large tables, checklist, common mistakes) that could arguably be split out, making the overview heavier than ideal. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- samber/cc-skills-golang
- Commit
e9761db
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.