Name: golang-performance
Rating: 72 (1 reviews)
Author: samber

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 `samber/cc-skills-golang@golang-benchmark` skill) or debugging workflow (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).

Quality

88%

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

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-architected skill body: clear methodology workflow with validation checkpoints, efficient tables, and clean progressive disclosure to verified reference files. Minor trimming of the opening preamble would improve conciseness.

Suggestions

Tighten the Persona/Thinking mode/Orchestration mode preamble — it reads as boilerplate and could be condensed without losing operational value.

Consider inlining one small concrete code snippet (e.g. a minimal atomic benchmark skeleton) so the body is self-contained for the most common entry point.

Dimension	Reasoning	Score
Conciseness	Largely lean with token-efficient tables (Decision Tree, Common Mistakes) and assumes Claude's competence, though the persona/thinking-mode/orchestration preamble and Core Philosophy prose could be trimmed slightly.	4 / 5
Actionability	Provides concrete executable commands ('go test -bench=... -benchmem -count=6 ... \| tee /tmp/report-1.txt', 'benchstat /tmp/report-1.txt /tmp/report-2.txt') and specific fixes (slog.LogAttrs, GOMEMLIMIT 80-90%), with the bulk of code patterns appropriately delegated to reference files.	4 / 5
Workflow Clarity	The iterative cycle (Define → Benchmark → Diagnose → Improve → Compare → Commit → Repeat) is a clearly sequenced workflow with an explicit validation checkpoint (benchstat for statistical significance) and a feedback loop (Repeat with incremented report number).	5 / 5
Progressive Disclosure	The body is a concise overview with well-signaled one-level-deep references (Deep Dives links to references/memory.md, cpu.md, etc., all verified to exist), plus a Cross-References section for sibling skills; content is appropriately split with deep detail in reference files.	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, well-scoped description that states concrete capabilities, gives explicit usage triggers, and cleanly separates itself from adjacent skills. Only minor gap: a few colloquial trigger phrases (slow, latency) are absent.

Suggestions

Add a couple of colloquial trigger terms (e.g. 'slow Go code', 'high latency', 'reduce memory usage') to broaden natural-language match.

Consider mentioning the .go file context briefly so file-extension-based triggers align with the rest of the ecosystem.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both what ('optimization patterns and methodology ... Covers ...') 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	Includes natural terms users say ('profiling', 'benchmarks', 'bottleneck', 'performance code review', 'performance gains') with synonyms, but misses a few common phrasings like 'slow code' or 'latency' that a user might naturally say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Go-performance niche and explicitly disambiguates from sibling skills ('Not for measurement methodology → See golang-benchmark ... or debugging workflow → See golang-troubleshooting'), minimizing 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: samber/cc-skills-golang
Path: skills/golang-performance/SKILL.md
Commit: 19a0626

Reviewed: 1 day 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.