golang-performance

Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (see golang-benchmark skill) or debugging workflow (see golang-troubleshooting skill).

0.97x

Quality

88%

Does it follow best practices?

Impact

84%

0.97x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is golang-performance in samber/cc-skills-golang

Quality

Content

85%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 performance skill: lean, actionable methodology with explicit validation checkpoints, and clean one-level-deep progressive disclosure to real reference files. Minor trimming of the duplicated ~80% claim and a few inline optimization snippets would push conciseness and actionability to full marks.

Suggestions

De-duplicate the '~80% of the time' intuition claim between Core Philosophy and the Common Mistakes table to tighten conciseness.

Inline one or two short copy-paste optimization snippets (e.g. a sync.Pool or preallocation example) for the most common cases so the body is self-sufficient beyond methodology.

Keep benchmark/regression commands as-is but consider flagging version-sensitive items (e.g. b.Loop() Go 1.24+) in a dedicated notes section rather than only in cross-references.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's Go competence and uses dense tables and pointers with no concept padding, but the '~80% of the time' intuition claim is repeated in both Core Philosophy and the Common Mistakes table, a minor redundancy that keeps it just below lean.	4 / 5
Actionability	Concrete executable commands appear throughout (e.g. 'go test -bench=BenchmarkMyFunc -benchmem -count=6 ./pkg/... \| tee /tmp/report-1.txt', 'benchstat /tmp/report-1.txt /tmp/report-2.txt', 'GOMEMLIMIT to 80-90%'), but the actual optimization patterns are delegated to references/ rather than given inline, leaving minor gaps.	4 / 5
Workflow Clarity	The Iterative Optimization Methodology is an explicit 8-step sequence (Define → Benchmark → Baseline → Diagnose → Improve → Compare → Commit → Repeat) with an explicit benchstat validation gate and a repeat feedback loop, plus a 'Rule Out External Bottlenecks First' pre-check.	5 / 5
Progressive Disclosure	The body is a clean overview with well-signaled one-level-deep references to real files (memory.md, cpu.md, io-networking.md, runtime.md, caching.md, observability.md) and a Deep Dives list with one-line summaries, with no nested references.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific description with concrete capabilities, explicit use-when triggers, and clear disambiguation from sibling skills. Voice is correctly third person throughout. The only mild gap is trigger-term breadth leaning technical rather than colloquial.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete optimization actions — 'allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization' — giving comprehensive coverage of the domain rather than vague abstraction.	5 / 5
Completeness	Explicitly states both what ('optimization patterns and methodology' with the enumerated sub-areas) and when ('Use when profiling or benchmarks have identified a bottleneck', 'Also use when performing performance code review'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers like 'profiling or benchmarks have identified a bottleneck' and 'performance code review' are present, but coverage leans technical (GC tuning, hot-path, pooling) and misses some plain-user synonyms like 'slow Go code' or 'make my Go faster'.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Golang performance optimization) with distinct triggers and explicit negative boundaries ('Not for measurement methodology (see golang-benchmark skill) or debugging workflow (see golang-troubleshooting skill)') that actively reduce conflict risk.	5 / 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: Vonage/cloud-runtime-cli
Path: .agents/skills/golang-performance/SKILL.md
Commit: f4b9df0

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