golang-patterns

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-TW/skills/golang-patterns/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A comprehensive, actionable Go patterns reference with executable code and commands throughout, well-organized into navigable sections. Its main weaknesses are length (content that could be split into bundle files is all inline) and the absence of any multi-step workflow with validation checkpoints.

Suggestions

Move the detailed linter config, anti-pattern catalog, and per-pattern deep dives into reference files (e.g. references/linting.md, references/anti-patterns.md) and keep SKILL.md as a concise overview with one-level-deep links.

Trim redundant good/bad example pairs where the good example alone conveys the pattern, to reduce token cost.

Add a short sequenced workflow for at least one common task (e.g. 'write a Go feature: define interface at consumer -> implement -> wrap errors -> add table-driven tests -> go vet/test') with an explicit validation checkpoint.

Dimension	Reasoning	Score
Conciseness	It assumes Claude's competence (no basic-concept padding) and uses lean prose with code, but at ~670 lines with many good/bad comparison pairs and a full linter config inline, it includes redundant illustrations that could be tightened, so it is mostly efficient rather than lean.	2 / 3
Actionability	It provides complete, executable Go code (e.g. WorkerPool, errgroup, functional options) plus copy-paste-ready commands ('go test -race ./...', 'gofmt -w .', 'golangci-lint run'), matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Content is organized into clear sections and lists 'when to enable' triggers, but as a pattern catalog it has no sequenced multi-step workflow with explicit validation checkpoints, and the simple-skill exception does not apply to this broad reference skill.	2 / 3
Progressive Disclosure	It is well-sectioned (not a wall of text) and the quick-reference table aids navigation, but no bundle files exist and all content — including the linter config, anti-patterns, and detailed examples that could live in separate reference files — is inline, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is Go-specific and distinct, but relies on abstract terms ('patterns, best practices, conventions') instead of concrete actions and omits any explicit 'Use when' trigger guidance. It answers 'what' well but leaves 'when' only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing, reviewing, or refactoring Go code, or when designing Go packages/modules.'

Replace abstract categories with concrete actions the skill performs (e.g. 'apply error-wrapping, interface, and concurrency patterns') to raise specificity.

Include common user variations such as 'Golang' and 'Go code review' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Idiomatic Go patterns') and an action ('building ... Go applications'), but 'best practices, and conventions' are abstract categories rather than concrete actions like 'extract' or 'fill', so it is not comprehensive enough for a 3.	2 / 3
Completeness	It clearly states what the skill covers (Go patterns/conventions for building applications) but includes no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'Go', 'patterns', and 'best practices' are relevant natural keywords a developer might say, but common variations such as 'Golang', 'Go code', or 'Go refactoring' are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'Idiomatic Go patterns ... Go applications' carves out a clear, language-specific niche that is unlikely to trigger for non-Go tasks, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 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
skill_md_line_count	SKILL.md is long (675 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: ysyecust/everything-claude-code
Path: docs/zh-TW/skills/golang-patterns/SKILL.md
Commit: a9cbecb

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