golang-pro

Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.

1.29x

Quality

85%

Does it follow best practices?

Impact

92%

1.29x

Average score across 3 eval scenarios

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

77%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.

Well-structured body with strong workflow sequencing, validation checkpoints, and exemplary progressive disclosure via a reference table pointing to real files. Conciseness is the main weakness, dragged down by a fluffy intro and a redundant keyword-list coda.

Suggestions

Remove the 'Senior Go developer with deep expertise...' intro paragraph — it restates the description and tells Claude nothing actionable.

Delete the trailing 'Knowledge Reference' keyword list; those terms already appear in the description, triggers, and Reference Guide, making it pure padding.

Make 'Output Templates' concrete by showing the expected file/package skeleton (e.g. a sample main.go + _test.go layout) instead of listing abstract deliverables.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the opening 'Senior Go developer with deep expertise...' sentence and the trailing 'Knowledge Reference' keyword dump restate capabilities already in the description and could be trimmed.	3 / 5
Actionability	Provides executable Go code, concrete commands ('go vet ./...', 'golangci-lint run', '-race'), and crisp MUST DO/MUST NOT DO constraints; the 'Output Templates' section stays somewhat abstract ('Interface definitions (contracts first)') rather than giving concrete scaffolding.	4 / 5
Workflow Clarity	A clear six-step Core Workflow with explicit validation gates — 'run go vet ./... before proceeding', 'fix all reported issues before proceeding', 'confirm race detector passes before committing' — plus a MUST DO/MUST NOT DO checklist acting as a feedback loop.	5 / 5
Progressive Disclosure	A clean Reference Guide table maps topics to real one-level-deep files (concurrency.md, interfaces.md, generics.md, testing.md, project-structure.md — all present) with a 'Load When' column for easy navigation.	5 / 5
	Total	17 / 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, third-person description that names concrete capabilities and gives explicit 'Use when'/'Invoke for' trigger guidance with good keyword coverage. The only gap is the absence of the '.go' file extension as a natural trigger term.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Implements concurrent Go patterns using goroutines and channels', 'designs and builds microservices with gRPC or REST', 'optimizes Go application performance with pprof', 'enforces idiomatic Go with generics, interfaces, and robust error handling' — giving comprehensive capability coverage.	5 / 5
Completeness	Explicitly answers both 'what' (the action list) and 'when' ('Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems' plus 'Invoke for...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, table-driven testing') with Go/Golang synonyms, but no file extension like '.go' that a user might naturally mention.	4 / 5
Distinctiveness Conflict Risk	A clear Go-language niche with distinct Go-specific triggers (goroutines, channels, gRPC, generics) makes conflict with other skills unlikely despite adjacency to microservices-architect.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: jeffallan/claude-skills
Path: skills/golang-pro/SKILL.md
Commit: 882ef55

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.