golang-performance
Optimize Go Performance With Profiling
Go services often slow down from allocations, GC pressure, I/O waits, or inefficient hot paths. This skill maps profiling signals to focused Go performance fixes and benchmark validation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "golang-performance" from https://skillstore.io/skills/samber-golang-performance.md and its manifest at https://skillstore.io/api/skills/samber-golang-performance/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "golang-performance". A handler has high latency but low CPU use.
Expected outcome:
The response should first check off-CPU waits, blocked goroutines, tracing spans, and upstream calls before micro-optimizing code.
Using "golang-performance". A heap profile shows many short-lived buffer allocations.
Expected outcome:
The response should compare slice reuse, bounded pooling, and safe copy rules, then ask for benchmark validation.
Using "golang-performance". A benchmark shows a loop dominates CPU time.
Expected outcome:
The response should inspect algorithmic complexity, inlining, cache locality, and direct indexing before suggesting lower-level changes.
Security Audit
SafeAll static findings were adjudicated as false positives. The matches occur in Markdown documentation, JSON evaluation prompts, example Go snippets, local profiling commands, or project metadata, with no evidence of malicious execution, exfiltration, prompt injection, or unauthorized file access.
Risk Factors
⚙️ External commands (80)
🌐 Network access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/samber-golang-performance/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/samber-golang-performance?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/samber-golang-performance?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-performance/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/samber-golang-performance.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
samber. (2026). golang-performance security audit report (audit version 3) [Author version 1.2.2]. Skillstore. https://skillstore.io/skills/samber-golang-performance/audits/3BibTeX citation
@techreport{samber-samber-golang-performance-2026,
author = {samber},
title = {golang-performance security audit report (audit version 3)},
institution = {Skillstore},
year = {2026},
number = {3},
url = {https://skillstore.io/skills/samber-golang-performance/audits/3},
note = {Author version 1.2.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-performance security audit report (audit version 3)"
version: "1.2.2"
type: report
authors:
- name: "samber"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/samber-golang-performance/audits/3"
identifiers:
- type: other
value: "skillstore:samber-golang-performance:audit:3"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
89jobrien-golang-performance
2026-08-21
samber-golang-performance
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review a Slow API Handler
Identify whether latency comes from Go code, database calls, network waits, allocations, or JSON overhead.
Reduce Allocation Pressure
Use heap profiles and benchmarks to choose slice, map, pooling, or copy strategies.
Prevent Performance Regressions
Add benchmark comparisons, Prometheus checks, and documentation for optimized hot paths.
Try These Prompts
My Go service is slow, but I do not know the bottleneck. Help me choose profiling steps before changing code.
I have a heap profile showing high allocations in a Go function. Explain likely causes and propose one benchmarked change at a time.
This Go function dominates CPU time in pprof. Review it for inlining, cache locality, allocation, and algorithmic improvements.
Help me create benchmark, benchstat, and observability checks that catch Go performance regressions before release.
Best Practices
- Profile first, choose one hypothesis, change one thing, and compare with benchstat.
- Prefer allocation reduction and algorithmic fixes before runtime tuning or unsafe code.
- Document optimized hot paths with benchmark numbers and the reason for the pattern.
Avoid
- Optimizing code from intuition without pprof, tracing, or benchmark evidence.
- Applying many performance changes at once without isolating the effect of each change.
- Using unsafe, pooling, or SIMD before proving a measured hot-path benefit.