jbvc/go-concurrency-patterns
Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.
65
65%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 a solid description with explicit 'Use when' triggers and good keyword coverage for Go concurrency topics. Its main weakness is that it leans toward listing concepts rather than describing concrete actions the skill performs (e.g., 'Master Go concurrency' is somewhat vague as an action). The use of imperative voice ('Master') rather than third person ('Teaches/Guides') is a minor style issue but doesn't severely impact utility.
Suggestions
Replace 'Master Go concurrency with...' with specific third-person actions like 'Implements goroutine patterns, designs channel pipelines, configures sync primitives, and manages context propagation in Go.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Go concurrency) and lists relevant concepts (goroutines, channels, sync primitives, context), but doesn't describe concrete actions like 'implement worker pools', 'detect race conditions', or 'design channel pipelines' — it mostly lists topics rather than specific actions the skill performs. | 2 / 3 |
Completeness | Clearly answers both 'what' (Go concurrency with goroutines, channels, sync primitives, context) and 'when' (building concurrent Go applications, implementing worker pools, debugging race conditions) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'goroutines', 'channels', 'sync primitives', 'context', 'worker pools', 'race conditions', 'concurrent Go applications'. These cover a good range of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Go concurrency specifically, with distinct triggers like 'goroutines', 'channels', 'race conditions', and 'worker pools' that are unlikely to conflict with general Go skills or concurrency skills in other languages. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a stub that defers all substantive content to an external file while providing only generic, non-actionable instructions in the main body. It lacks any concrete Go concurrency code, patterns, or specific guidance. The instructions read as boilerplate that could apply to any topic and fail to leverage the SKILL.md as a useful overview.
Suggestions
Add at least one concrete, executable Go code example in the SKILL.md body (e.g., a basic goroutine + channel pattern or worker pool snippet) so the skill provides immediate value without requiring the external file.
Replace the generic instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') with concurrency-specific guidance such as key rules (e.g., 'Always use context for cancellation', 'Never start a goroutine without a shutdown path').
Add a quick-reference section summarizing the most common patterns (e.g., fan-out/fan-in, worker pool, pipeline) with brief descriptions before pointing to the playbook for full implementations.
Include at least a brief workflow for debugging race conditions (e.g., 'Run with -race flag → identify the race → apply mutex or channel fix → re-run with -race to verify').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively short but includes generic filler instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that add no value for Claude. The 'Do not use' section is also boilerplate. However, it's not excessively verbose. | 2 / 3 |
Actionability | There are no concrete code examples, commands, or specific patterns. The instructions are entirely vague and abstract ('Apply relevant best practices and validate outcomes'). Everything actionable is deferred to an external file with no inline guidance. | 1 / 3 |
Workflow Clarity | There is no clear workflow, sequence of steps, or validation checkpoints. The instructions are generic bullet points that could apply to any skill, with no concurrency-specific process guidance. | 1 / 3 |
Progressive Disclosure | There is a reference to a detailed resource file (resources/implementation-playbook.md), which is good progressive disclosure structure. However, the SKILL.md itself provides essentially zero useful overview content—it's an empty shell pointing elsewhere, making the reference less useful without any inline quick-start content. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents