Name: golang-benchmark
Rating: 72 (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

89%

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

78%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 strong, actionable body with excellent progressive disclosure and executable examples covering the full benchmark→profile→compare→CI workflow. The main weakness is conciseness: some rationale paragraphs and inline Go-version specifics could be trimmed or sectioned off.

Suggestions

Tighten the editorial rationale paragraphs (e.g. the _bench_test.go naming rationale and the noisy-neighbor explanation) to the essential rule, moving the 'why' to a single sentence.

Consolidate version-sensitive notes (Go 1.24+ b.Loop, 1.26 inlining fix, 1.17+ optional metrics) into a dedicated 'Version notes' or compatibility section rather than scattering them inline, so they don't penalize readability as they age.

Optional: render the top-level measurement workflow as a short numbered checklist with an explicit 'verify statistical significance before claiming a win' checkpoint, mirroring the structure already used in the parallel-variants section.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code and a flag table, but several editorial rationale paragraphs (file-naming conventions, the noisy-neighbor explanation) could be tightened, and inline version-sensitive statements ('Go 1.24+', 'Go 1.26 fixed an earlier b.Loop() inlining limitation', 'Go 1.17+') are scattered rather than isolated in a version/deprecated section.	3 / 5
Actionability	Provides copy-paste-ready, executable guidance throughout — b.Loop()/ReportAllocs/ReportMetric code, table-driven sub-benchmarks, the run command with a flag table, profiling commands, and a concrete commit-message format with a real benchstat output example.	5 / 5
Workflow Clarity	The end-to-end measurement workflow (write → run → profile → compare with benchstat → gate in CI) is clearly sequenced, and the parallel-variants section has explicit checkpoints (run serially, compare against the same baseline, keep the winner, ExitWorktree), though the overall flow is narrative rather than a strict numbered checklist with validate→fix→retry loops.	4 / 5
Progressive Disclosure	SKILL.md is a lean overview that signals one-level-deep references to real bundle files (pprof.md, benchstat.md, trace.md, tools.md, compiler-analysis.md, ci-regression.md, investigation-session.md, prometheus-go-metrics.md, all present in ./references/) each with a one-line purpose, plus clear cross-references to sibling skills.	5 / 5
	Total	17 / 20 Passed

Description

100%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.

An exemplary description: it states concrete capabilities, gives explicit 'Use when' triggers with natural vocabulary, and cleanly separates its measurement role from a sibling optimization skill. No vague fluff or over-claims are present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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', 'investigating production performance with Prometheus runtime metrics' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (benchmarking/profiling/performance measurement with the listed actions) and 'when' via two clear 'Use when...' trigger clauses, including a secondary one for deep analysis on a specific performance indicator.	5 / 5
Trigger Term Quality	Covers the natural terms a developer would actually say — 'Go benchmarks', 'pprof', 'CPU/memory/trace profiles', 'benchstat', 'CI benchmark regression', 'Prometheus runtime metrics' — with relevant synonyms and tool names rather than generic jargon.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche (measurement methodology) and explicitly distinguishes it from the sibling optimization skill ('this skill provides the measurement methodology, while golang-performance provides the optimization patterns'), minimizing wrong-skill triggering.	5 / 5
	Total	20 / 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: 30cdf15

Reviewed: 5 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.