Go Benchmarking Skill for Muse
Statistically sound Go benchmarks, profiles, CI gating.
- What
- Statistically sound Go benchmarks, profiles, CI gating.
- Cost
- Free
- Needs
- a Go toolchain (go binary) on your machine; benchstat — install with `go install golang.org/x/perf/cmd/benchstat@latest` if not present. No API keys. Designed for Claude Code, Codex or a similar coding-agent harness, on projects using Golang.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
The measurement side of Go performance work: writing benchmarks (b.Loop on Go 1.24+, memory tracking with -benchmem, table-driven sub-benchmarks, sink discipline against dead-code elimination), running them right (output format, flags, -count for significance), comparing with benchstat (confidence intervals, p-values, hardware context lines, what to strip from commit messages), profiling from benchmark runs (CPU/mem profiles, execution trace), and guarding CI against regressions (benchdiff, cob, gobenchdata, noisy-neighbor mitigation, self-hosted runner tuning). A companion to golang-troubleshooting and golang-performance in the same repo — it does the measuring, the others do the fixing. Expects a Go toolchain plus benchstat (installed via go install golang.org/x/perf/cmd/benchstat@latest). Discovered via skills.sh. Honest note: it is statistically rigorous by design — never trust a single run, and a benchstat delta straddling the Go 1.26→1.27 toolchain boundary measures the toolchain (allocator changes) not your code; cloud CI benchmarks wobble 5–10% even on quiet machines. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @samber.
Version:
Quick answer
Go Benchmarking Skill for Muse is a free Muse skill that teaches statistically sound Go benchmarks, profiles, and CI gating, covering benchmark writing, running them right, comparing with benchstat, profiling from benchmark runs, and guarding CI against regressions. It is the measurement side of Go performance work, for results you can trust.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 8e899e2Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Go toolchain (go binary) on your machine; benchstat — install with `go install golang.org/x/perf/cmd/benchstat@latest` if not present. No API keys. Designed for Claude Code, Codex or a similar coding-agent harness, on projects using Golang. Install "Go Benchmarking Skill for Muse" for me. Go benchmarking and performance measurement — writing benchmarks (b.Loop, memory tracking, table-driven sub-benchmarks), running them with statistical rigor (-count, flags), comparing with benchstat (confidence intervals, p-values), pprof/trace interpretation from benchmark runs, and CI regression detection (benchdiff, cob, gobenchdata). Repository: https://raw.githubusercontent.com/samber/cc-skills-golang/8e899e20ff0cd4dc524af3993e4c62d8ee8c5717/skills/golang-benchmark/SKILL.md Pinned version: install the code at commit 8e899e20ff0cd4dc524af3993e4c62d8ee8c5717 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files: references/) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "golang-benchmark". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the go toolchain and benchstat via go install if missing). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- installs packages — Prerequisites: a Go toolchain (go binary) on your machine; benchstat — install with `go install golang.org/x/p · Prérequis : une toolchain Go (binaire go) sur votre machine ; benchstat — à installer avec `go install golang. · 5. Indiquez ce qui a été installé, où, et ce qu'il me reste à faire moi-même (ex. installer la toolchain Go et
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 8e899e2 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : installs packages
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.