Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Golang Pro · dokhacgiakhoa | DecimalAI

dokhacgiakhoa/golang-pro

SkillScore45Maintained

Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Expert in the latest Go ecosystem including generics, workspaces, and cutting-edge frameworks. Use PROACTIVELY for Go development, architecture design, or performance optimization.

codingby dokhacgiakhoa

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/dokhacgiakhoa-golang-pro/SKILL.md

decimalai skills pull dokhacgiakhoa-golang-pro --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/dokhacgiakhoa-golang-pro/SKILL.md https://app.decimal.ai/s/dokhacgiakhoa-golang-pro/SKILL.md

Raw file: /s/dokhacgiakhoa-golang-pro/SKILL.md ↗ · machine-readable summary at /s/dokhacgiakhoa-golang-pro.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 24d ago

Yes — +18% lift+6% tokens0% turns45% of whole cases pass with skill (10/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	-9%	0%
case-05	✗→✓	▲ Improved	-47%	0%
case-06	✗→✓	▲ Improved	-79%	0%
case-10	✗→✓	▲ Improved	32%	0%
case-04	✓→✓	＝ Same ✓	21%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/10/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

dokhacgiakhoa / agent-skills-4-vibe-coding-cli

.agent/skills/golang-pro/SKILL.md

View on GitHub ↗

License NOASSERTIONImported 8/10/2026Version v1

Skill contents

SKILL.md

You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.

Use this skill when

Building Go services, CLIs, or microservices
Designing concurrency patterns and performance optimizations
Reviewing Go architecture and production readiness

Do not use this skill when

You need another language or runtime
You only need basic Go syntax explanations
You cannot change Go tooling or build configuration

Instructions

Confirm Go version, tooling, and runtime constraints.
Choose concurrency and architecture patterns.
Implement with testing and profiling.
Optimize for latency, memory, and reliability.

Purpose

Expert Go developer mastering Go 1.21+ features, modern development practices, and building scalable, high-performance applications. Deep knowledge of concurrent programming, microservices architecture, and the modern Go ecosystem.

Capabilities

🧠 Knowledge Modules (Fractal Skills)

1. Modern Go Language Features

2. Concurrency & Parallelism Mastery

3. Performance & Optimization

4. Modern Go Architecture Patterns

5. Web Services & APIs

6. Database & Persistence

7. Testing & Quality Assurance

8. DevOps & Production Deployment

9. Modern Go Tooling

10. Security & Best Practices

Illustrative Want to see what dokhacgiakhoa/golang-pro would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/30/2026, 08:33 UTC · 22 cases

Lift

+18%

45% vs 27%

Agent turns

1.0 vs 1.0

Tokens

+6%

3,690.64 vs 3,476.09

fail → pass · 4pass → pass · 6fail → fail · 12

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 We need to build a high-throughput stream processor in Go for our data pipeline that handles thousands of incoming webhooks per second. Please design and implement the service architecture, including worker pools for concurrent job processing, context cancellation for graceful shutdowns, and a unit/benchmark testing suite. Provide the full code layout and performance optimization steps.	fail→pass	38,129	39,010	+2%	1	1	0%	8,255	7,537	-9%	0	0	—
case-02 I'm refactoring an older Go microservice to modern Go standards (1.21+). Can you review our architectural layout and propose a clean, production-ready structure? Include a complete implementation pattern for persistent storage integration, structured logging, custom domain error handling, and a strategy for profiling memory usage under load.	fail→fail	41,097	27,558	-33%	1	1	0%	7,763	5,263	-32%	0	0	—
case-03 We are building a command-line utility in Go to parse and aggregate gigabytes of log files fast without ballooning memory usage. Please write a production-grade implementation using modern Go concurrent primitives, efficient file scanning techniques, and a complete guide for profiling CPU/memory bottlenecks alongside integration tests.	fail→fail	46,616	39,028	-16%	1	1	0%	8,247	8,691	+5%	0	0	—
case-04 I am learning Go for the first time. Can you explain basic syntax for declaring variables, using `if` statements, and writing simple `for` loops with basic beginner examples?	pass→pass	16,771	16,750	-0%	1	1	0%	2,297	2,788	+21%	0	0	—
case-05 Our company deploys Go binaries to legacy hardware using a fixed, unchangeable Go 1.10 toolchain where we cannot modify build flags, update Go tooling, or change compiler configurations. Can you help us configure a Go 1.21+ build pipeline for this setup?	fail→pass	22,997	11,929	-48%	1	1	0%	3,112	1,642	-47%	0	0	—
case-06 We are building a concurrent microservice in Rust using the Tokio async runtime and hyper HTTP web framework. Can you write the service implementation and async task pool in Rust?	fail→pass	28,524	8,461	-70%	1	1	0%	4,835	1,034	-79%	0	0	—
case-07 We need a helper function to deduplicate and sort a slice of structs by ID in our Go service. A teammate suggested writing custom nested loops with a manual map lookup. How should this be implemented in Go 1.21+ using standard library capabilities?	pass→pass	13,582	23,702	+75%	1	1	0%	2,630	4,050	+54%	0	0	—
case-08 Our HTTP service cancels database contexts on timeouts, but downstream telemetry cannot determine whether the cancellation was caused by a database query deadline or an explicit cancellation signal. Developers currently call `context.WithTimeout`. How can we attach explicit cancellation error causes in Go 1.21+?	pass→pass	17,150	14,841	-13%	1	1	0%	2,421	3,409	+41%	0	0	—
case-09 We want to replace `log.Printf` and third-party loggers with standard library structured JSON logging in Go 1.21+. A junior developer proposed writing custom `fmt.Sprintf` JSON formatter functions. How should structured logging be implemented?	fail→fail	20,525	19,429	-5%	1	1	0%	2,777	3,311	+19%	0	0	—
case-10 Our network protocol handler allocates thousands of temporary `[]byte` buffers per second, causing frequent GC pauses. A team member suggested setting `GOGC=500`. What is the idiomatic Go memory reuse pattern for temporary buffers?	fail→pass	21,712	23,010	+6%	1	1	0%	2,856	3,775	+32%	0	0	—
case-11 We need to execute three HTTP requests in parallel. If any request fails, all other pending requests must cancel immediately, and the first error should return. Current code uses `sync.WaitGroup` with manual error channel collection. What pattern should be used?	fail→fail	13,975	14,177	+1%	1	1	0%	1,848	2,257	+22%	0	0	—
case-12 In an asynchronous processing loop `for _, task := range tasks { go func() { process(task) }() }`, older Go versions required passing `task` as a parameter to avoid closure bugs. What is the loop variable behavior in modern Go (1.22+)?	fail→fail	11,547	11,716	+1%	1	1	0%	1,242	1,681	+35%	0	0	—
case-13 We store an application configuration struct read by millions of concurrent HTTP request handlers. The config updates once a day. Developers currently guard reads with a `sync.RWMutex`. What is the zero-lock concurrency pattern in Go for atomic pointer replacement?	fail→fail	16,373	18,374	+12%	1	1	0%	2,104	2,905	+38%	0	0	—
case-14 Our REST API service experiences sudden memory spikes under heavy load. We need a systematic procedure and code setup to profile memory allocations and identify heap memory leaks. How should this be implemented?	pass→pass	25,763	19,318	-25%	1	1	0%	3,911	4,076	+4%	0	0	—
case-15 We have multiple custom numeric types and need a generic utility function that returns the minimum and maximum of two values without writing separate functions per type or using interface reflection. How should this be written in Go 1.21+?	fail→fail	9,545	11,054	+16%	1	1	0%	1,813	2,577	+42%	0	0	—
case-16 We are designing a user management microservice in Go. The team is debating writing SQL queries directly inside HTTP handler functions. How should layer separation be structured for production maintainability?	fail→fail	22,745	21,024	-8%	1	1	0%	3,292	4,721	+43%	0	0	—
case-17 During Kubernetes deployments, our Go HTTP services abruptly close active client connections when SIGTERM is received. How do we implement clean graceful shutdown?	fail→fail	22,515	27,774	+23%	1	1	0%	3,295	4,896	+49%	0	0	—
case-18 Processing thousands of background jobs by spawning an unbounded number of goroutines `go process(job)` causes out-of-memory crashes during traffic spikes. How should concurrency be limited in Go?	fail→fail	16,393	14,501	-12%	1	1	0%	3,018	3,133	+4%	0	0	—
case-19 Our service logs errors formatted with `fmt.Errorf("failed: %v", err)`, which loses original error types and prevents callers from inspecting root causes. How should error wrapping and inspection be implemented?	pass→pass	11,993	16,726	+39%	1	1	0%	2,187	2,732	+25%	0	0	—
case-20 Our PostgreSQL connection pool in Go frequently exhausts connections during sudden traffic surges, returning connection refused errors. How should the connection pool parameters in `database/sql` be configured?	fail→fail	16,927	14,573	-14%	1	1	0%	3,002	2,971	-1%	0	0	—
case-21 Our Go service makes outbound REST calls using `http.DefaultClient`. During downstream network outages, HTTP calls hang indefinitely, consuming server worker threads. How should HTTP clients be safely constructed?	fail→fail	14,465	22,693	+57%	1	1	0%	2,756	3,982	+44%	0	0	—
case-22 Our unit test suite contains dozens of copy-pasted test functions for input string sanitization logic. How should this test suite be refactored using standard Go testing patterns?	pass→pass	19,473	22,358	+15%	1	1	0%	2,813	3,763	+34%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +18 percentage points is the difference between those two pass rates over the 22 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 27.3%
Pass rate with the skill: 45.5%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 0
Skill version measured: v1
Run completed: 8/30/2026, 08:33 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

We need to build a high-throughput stream processor in Go for our data pipeline that handles thousands of incoming webhooks per second. Please design and implement the service architecture, including worker pools for concurrent job processing, context cancellation for graceful shutdowns, and a unit/benchmark testing suite. Provide the full code layout and performance optimization steps.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run45

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+28% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 23 days ago

Other measured skills in the registry, with their headline benchmark lift.