golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skills-golang@golang-performance` provides the optimization patterns.
73
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 hits all the marks. It lists specific concrete actions and tools, includes a comprehensive 'Use when...' clause with natural trigger terms, and explicitly distinguishes itself from a closely related skill. The description is detailed yet focused, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing/running/comparing benchmarks, profiling with pprof, interpreting CPU/memory/trace profiles, analyzing with benchstat, CI benchmark regression detection, and investigating production performance with Prometheus runtime metrics. | 3 / 3 |
Completeness | Clearly answers both 'what' (benchmarking, profiling, performance measurement with specific tools) and 'when' (explicit 'Use when...' clause listing multiple trigger scenarios). Also distinguishes itself from a related skill by clarifying scope boundaries. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'benchmarking', 'profiling', 'Go benchmarks', 'pprof', 'CPU/memory/trace profiles', 'benchstat', 'CI benchmark regression', 'Prometheus', 'performance', 'hot paths'. These are all terms a Go developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carves out a distinct niche focused on measurement/profiling vs optimization patterns, and explicitly differentiates itself from the related `golang-performance` skill. The specific tool mentions (pprof, benchstat, Prometheus) make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides a complete Go benchmarking workflow with executable examples, statistical rigor emphasis, and excellent progressive disclosure to reference files. The main weakness is mild verbosity in the Reference Files section where each entry has a full explanatory paragraph that could be trimmed. Overall, it's highly actionable and well-organized for its complexity.
Suggestions
Trim the Reference Files section — the one-sentence descriptions after the bold links are sufficient; the additional 'Use this when...' sentences are largely inferrable and add token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The main body is reasonably efficient with good code examples and tables, but the Reference Files section is verbose — each bullet has a full paragraph explaining when to use it, which is somewhat redundant given the descriptive titles and the fact that Claude can infer usage context. The commit documentation section is useful but lengthy. | 2 / 3 |
Actionability | Fully executable code examples for writing benchmarks (b.Loop, sub-benchmarks, memory tracking), concrete CLI commands for running and profiling, a complete flag reference table, and a specific commit message format with real benchstat output. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill follows a clear sequential workflow: write benchmark → run with statistical rigor (-count=10) → profile → compare with benchstat → document in commits → detect regressions in CI. The commit documentation section includes explicit validation rules (never paste results with '~', only include affected benchmarks), and the profiling section sequences CPU → memory → trace analysis logically. | 3 / 3 |
Progressive Disclosure | Excellent structure: the main SKILL.md covers the essential workflow concisely, then clearly signals 8 reference files for deep dives (pprof, benchstat, trace, tools, compiler analysis, CI regression, investigation sessions, Prometheus metrics). References are one level deep with descriptive summaries explaining when to use each. Cross-references to other skills are well-organized. | 3 / 3 |
Total | 11 / 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
8c7e016
- 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.