Name: golang-benchmark
Rating: 73.6 (1 reviews)
Author: samber

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable measurement skill with strong progressive disclosure via real reference files. The main weakness is time-sensitive version-specific guidance embedded in the main flow rather than isolated, and feedback loops that are implied rather than explicit.

Suggestions

Move the Go 1.24/1.26/1.27 version-specific notes into a dedicated "Version notes" or "Toolchain caveats" section so the main b.Loop guidance stays evergreen and token-efficient.

Add an explicit numbered validate→fix→retry loop for the CI regression and commit-documentation workflows (e.g., "if benchstat shows ~, increase -count and rerun before claiming the improvement").

Consider condensing the b.Loop vs b.N narrative into a short preference rule plus a one-line pointer, since most of the detail is toolchain-version context.

Dimension	Reasoning	Score
Conciseness	Mostly lean with tight code blocks and no padding of basic Go concepts, but version-specific prose ("Go 1.26 fixed an earlier b.Loop() inlining limitation", the Go 1.27 allocator paragraph) is time-sensitive material woven into the main b.Loop section rather than isolated in a version/deprecated note, which could be trimmed or relocated.	4 / 5
Actionability	Executable, copy-paste-ready guidance throughout — b.Loop() and b.ReportAllocs() examples, the `go test -bench` flag table, profiling commands, and a concrete benchstat commit-message template with a filled-in diff example covering common cases.	5 / 5
Workflow Clarity	A clear write→run→profile→compare→document→CI sequence is established in the intro and reflected in section order, with statistical-rigor checkpoints (count=10, same baseline, same toolchain, "never paste ~ results"); however explicit validate→fix→retry feedback loops are implied rather than spelled out as numbered steps.	4 / 5
Progressive Disclosure	SKILL.md is an overview with a dedicated Reference Files section giving one-line descriptions and links to all 8 real reference files (pprof, benchstat, trace, tools, compiler-analysis, ci-regression, investigation-session, prometheus-go-metrics), references are one level deep, and cross-references to sibling skills are clearly signaled.	5 / 5
	Total	18 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description with explicit what/when triggers and good natural keyword coverage. The only weakness is residual overlap with sibling Go performance/troubleshooting skills, partially mitigated by the explicit boundary statement.

Suggestions

Sharpen the boundary against golang-troubleshooting by stating that pprof setup on running services belongs to that skill (as the body already does) directly in the description.

Consider adding the .go file extension or "_bench_test.go" as an explicit trigger token to match how users refer to benchmark files.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions bound to specific tools — "writing, running, or comparing Go benchmarks", "profiling hot paths with pprof", "interpreting CPU/memory/trace profiles", "analyzing results with benchstat", "CI benchmark regression detection", "investigating production performance with Prometheus runtime metrics" — giving comprehensive coverage rather than abstract language.	5 / 5
Completeness	Explicitly answers both what (benchmarking/profiling/measurement with named tools) and when via two "Use when..." / "Also use when..." clauses with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases a user would actually say are well covered — "Go benchmarks", "profile with pprof", "benchstat", "CI benchmark regression", "Prometheus runtime metrics", "performance indicator" — including tool-specific synonyms rather than generic jargon.	5 / 5
Distinctiveness Conflict Risk	The benchmarking/benchstat niche is distinct and the description explicitly carves out measurement vs. optimization ("this skill provides the measurement methodology, while samber/cc-skills-golang@golang-performance provides the optimization patterns"), but pprof/profiling and Prometheus overlap with sibling golang-troubleshooting/observability skills, leaving minor overlap risk.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-benchmark/SKILL.md
Commit: 19a0626

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.