CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Well-structured content: an explicit gated workflow with validation checkpoints, concrete commands and idioms, and a clean one-level-deep reference table backed by real files. The main slack is the redundant "Knowledge Reference" keyword list, and the single code example could be made fully self-contained.

Suggestions

Delete the "Knowledge Reference" section — it is a keyword dump of concepts Claude already knows and duplicates the frontmatter description; the Reference Guide table already provides topic navigation.

Make the Core Pattern Example fully copy-paste ready by including the package clause and imports (context, fmt, time), per the actionability anchor for executable code.

DimensionReasoningScore

Conciseness

The body is mostly lean — the workflow, constraints, and code example all earn their tokens — but the "Knowledge Reference" section is a keyword list of concepts Claude already knows ("Go 1.21+, goroutines, channels, select, sync package, generics, ..."), duplicating the frontmatter description and adding no guidance. This is more than the 'minor trim' of anchor 5 but less severe than the padding pattern of anchor 3.

4 / 5

Actionability

Concrete and executable in most places: specific commands (`go vet ./...`, `golangci-lint run`, `-race`), specific conventions ("Propagate errors with fmt.Errorf(\"%w\", err)"), and a complete-looking worker/pipeline code example. It stops short of anchor 5 because the code example omits imports/package context and only covers one pattern (concurrency), while gRPC, generics, and testing rely on references rather than shown examples.

4 / 5

Workflow Clarity

The six-step Core Workflow has a clear sequence with explicit validation gates and feedback loops: "run `go vet ./...` before proceeding", "Run `golangci-lint run` and fix all reported issues before proceeding", and "confirm race detector passes before committing". This matches anchor 5's pattern of validate → fix → proceed, and exceeds anchor 4 where checkpoints would be present but without explicit retry/gating language.

5 / 5

Progressive Disclosure

The Reference Guide is a well-signaled table mapping each topic to an existing one-level-deep file (`references/concurrency.md`, `interfaces.md`, `generics.md`, `testing.md`, `project-structure.md` — all verified present) with an explicit "Load When" column. No reference file links further files, so navigation is flat and easy; this matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

88%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 description: specific, third-person, with explicit and concrete 'Use when'/'Invoke for' guidance. The only weaknesses are missing the common "Golang" synonym and a few generic trailing trigger terms that create minor overlap risk with non-Go skills.

Suggestions

Add the synonym "Golang" to the description (e.g., "Use when building Go/Golang applications...") since it appears only in metadata triggers and is the most common way users refer to the language.

Qualify the generic trigger terms "CLI tools, benchmarks, or table-driven testing" with the language (e.g., "Go CLI tools", "Go benchmarks") to reduce conflict risk with general-purpose coding skills.

DimensionReasoningScore

Specificity

The description 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" — comprehensively covering the skill's stated domains in third-person voice. Anchor 5 fits: multiple specific concrete actions with comprehensive coverage, not the minor-gaps profile of anchor 4.

5 / 5

Completeness

It explicitly answers both questions: what ("Implements concurrent Go patterns... designs and builds microservices... optimizes... enforces idiomatic Go") and when ("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."). Concrete trigger phrases match anchor 5 exactly; anchor 4 would require a vaguer 'when' clause.

5 / 5

Trigger Term Quality

Good natural-term coverage ("goroutines", "channels", "Go generics", "gRPC integration", "benchmarks", "table-driven testing") but a few common terms are missing — notably the synonym "Golang" (present only in metadata, not in the description) and variations like "Go server" or "Go API". It clearly exceeds anchor 3 (which would require missing common variations) but falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The Go niche is clear and most triggers (goroutines, channels, pprof, gRPC, Go generics) are language-distinct, but the trigger list ends with generic terms — "CLI tools, benchmarks, or table-driven testing" — which are not Go-specific and could cause overlap with general coding/testing skills. Mostly distinct with minor overlap risk fits anchor 4 better than anchor 5's 'minimal conflict risk', since those generic phrases stand alone as triggers.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.