Go Performance
CheckedHelps with Go, performance optimization as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add cxuu/golang-skills --skill go-performance -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
cxuu
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned cxuu/golang-skills at 91f0c2eef5.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 91f0c2eef5
- Manifest
- skills/go-performance/SKILL.md
- Scanned
- 4 files, 784 lines
About this skill
What it does
This skill provides guidance and tools for optimizing Go program performance within an agent workflow. It focuses on identifying and addressing bottlenecks in critical code sections ("hot paths") through techniques like using strconv instead of fmt for string conversions, avoiding repeated string-to-byte conversions, specifying container capacity when initializing maps and slices, and choosing appropriate string concatenation methods. The skill includes a script to benchmark Go code and compare results.
When to use it
- When debugging slow Go applications or services.
- During performance reviews of existing Go codebases.
- To optimize specific functions or loops identified as bottlenecks.
- When needing to improve the efficiency of string manipulation operations in Go.
- Before deploying a Go application to production, to ensure optimal resource usage.
Key capabilities
- Benchmarking: Runs Go benchmarks using
bench-compare.shwith optional baseline comparison viabenchstat. Results can be saved for future comparisons. - String Conversion Optimization: Recommends using
strconvoverfmtfor string conversions due to performance differences. - Byte Conversion Optimization: Suggests converting strings to byte slices once outside of loops to avoid repeated allocations.
- Container Capacity Hints: Provides guidance on specifying capacity when initializing maps and slices with
make(). - Pass-by-Value Guidance: Offers advice on avoiding unnecessary pointer usage in function arguments for small, fixed-size types like strings.
- String Concatenation Strategies: Suggests choosing the appropriate string concatenation method (
+,fmt.Sprintf,strings.Builder,strings.Join, backtick literals) based on complexity and context.
Example prompts
- "Analyze this Go code snippet for performance bottlenecks."
- "Benchmark this function using the provided script, comparing it to a previous version."
- "Suggest ways to optimize string conversions in this loop."
- "How can I improve the allocation efficiency of this map initialization?"
Tips & gotchas
- Focus optimization efforts on "hot paths"—the most frequently executed code sections. Premature optimization elsewhere is discouraged.
- The
bench-compare.shscript requires bash execution and may have specific command line options (run with--help). - Map capacity hints are approximations, not guarantees of complete preemptive allocation.