Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
97
100%
Does it follow best practices?
Impact
95%
1.17xAverage score across 6 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 comprehensively covers Go-specific capabilities with concrete actions, includes explicit 'Use when' and 'Invoke for' clauses with natural trigger terms, and uses proper third-person voice throughout. The description is well-structured, specific, and would allow Claude to accurately select this skill when users need Go development assistance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'implements concurrent Go patterns using goroutines and channels', 'designs and builds microservices with gRPC or REST', 'optimizes Go application performance with pprof', and 'enforces idiomatic Go with generics, interfaces, and robust error handling'. | 3 / 3 |
Completeness | Clearly answers both what (concurrent patterns, microservices, performance optimization, idiomatic Go) AND when with explicit 'Use when...' and 'Invoke for...' clauses that specify trigger scenarios like 'building Go applications requiring concurrent programming' and specific terms like 'goroutines, channels'. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'goroutines', 'channels', 'Go generics', 'gRPC', 'CLI tools', 'benchmarks', 'table-driven testing', 'microservices', 'concurrent programming', 'pprof'. These are terms Go developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Go-specific terminology (goroutines, channels, pprof, gRPC, table-driven testing) that clearly differentiates it from general programming skills or other language-specific skills. Unlikely to conflict with non-Go skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates best practices across all dimensions. It's concise yet comprehensive, provides executable code with clear validation checkpoints, and uses progressive disclosure effectively through a well-organized reference table. The MUST DO/MUST NOT DO constraints provide clear guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's Go competence. No unnecessary explanations of basic concepts—jumps straight to patterns, constraints, and actionable guidance. | 3 / 3 |
Actionability | Provides fully executable code example with proper context cancellation pattern, specific linting commands (golangci-lint run, go vet), and concrete MUST DO/MUST NOT DO constraints that are immediately actionable. | 3 / 3 |
Workflow Clarity | Clear 6-step workflow with explicit validation checkpoints: 'run go vet before proceeding', 'fix all reported issues before proceeding', 'confirm race detector passes before committing'. Feedback loops are built into the process. | 3 / 3 |
Progressive Disclosure | Excellent structure with a reference table pointing to one-level-deep topic files (references/concurrency.md, etc.) with clear 'Load When' guidance. Main content stays focused on overview and core patterns. | 3 / 3 |
Total | 12 / 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.
5b76101
Table of Contents
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.