golang-expert

Senior Go engineer and technical advisor — use for any Go question, design decision, or implementation task. Covers idiomatic patterns, concurrency, error handling, project structure, performance optimisation, observability, and testing. Invoke whenever the user is writing, reviewing, debugging, or designing Go code, asking about goroutines, channels, interfaces, generics, modules, or benchmarks, or wants a second opinion on a Go architecture. Triggers on: Go, Golang, goroutine, channel, interface, gRPC, go.mod, go test, pprof, golangci-lint.

Quality

86%

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

78%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 tight, well-structured Go skill body with executable examples, clear workflows, and clean progressive disclosure into verified reference files. Weakest spot is mild redundancy between the standards list and quick-reference, and a few code snippets with placeholders.

Suggestions

Dedupe the error-wrapping rule: keep it in the quick-reference and have the 'Non-negotiable standards' list point there rather than restating the %w convention twice.

Tighten code snippets to be copy-paste runnable — replace `SELECT ...` and the undeclared `u`/`err` in the GetUser example with minimal complete declarations.

Add an explicit validate-fix-retry loop to the Review and Debug workflows (e.g., 'fix → re-run go test -race → only close when green') to match the Implement workflow's rigor.

Dimension	Reasoning	Score
Conciseness	Lean, table-and-code-driven body that assumes Go competence and avoids explaining basics, but the 'Non-negotiable standards' list overlaps the quick-reference (error wrapping stated twice) and a few cross-reference lines could be trimmed.	4 / 5
Actionability	Provides concrete, mostly-executable code (errgroup, graceful shutdown, constructors) and exact commands (go test -race, golangci-lint run, go vet), but some snippets have placeholders/undeclared vars (SELECT ..., return &u) that stop just short of copy-paste-ready.	4 / 5
Workflow Clarity	Three numbered workflows with a validation checkpoint in the Implement flow (test -race / lint / vet); Review and Debug workflows are sequenced but lack explicit validate-fix-retry feedback loops, leaving minor gaps.	4 / 5
Progressive Disclosure	Clear overview with a well-signaled reference table linking five real one-level-deep files, each with a 'When to read' cue — easy navigation with content appropriately split between inline quick-reference and references.	5 / 5
	Total	17 / 20 Passed

Description

95%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-targeted description that clearly states both capabilities and explicit invocation triggers with comprehensive natural keywords. Minor room to sharpen abstract phrases like 'design decision'/'implementation task' into more concrete verbs.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('writing, reviewing, debugging, or designing Go code', 'second opinion on a Go architecture') plus a comprehensive coverage list (concurrency, error handling, generics, etc.), but the actions are somewhat abstract compared to verb-level anchors like 'extract'/'fill'.	4 / 5
Completeness	Explicitly answers both 'what' (senior Go engineer covering named topics) and 'when' ('Invoke whenever the user is writing, reviewing... Triggers on:'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms (Go/Golang), tooling (pprof, golangci-lint, go test), and file markers (go.mod) — matches the anchor covering synonyms and file-extension-style triggers.	5 / 5
Distinctiveness Conflict Risk	A clear Go-specific niche with distinct triggers (goroutine, channel, go.mod, gRPC) and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: rikdc/ai-skills
Path: plugins/dev-skills/skills/golang-expert/SKILL.md
Commit: cd15778

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