golang-patterns

构建健壮、高效且可维护 Go 应用程序的惯用法（Idiomatic Go）、最佳实践与规范。

Quality

57%

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/ja-JP/skills/golang-patterns/SKILL.md

Quality

Content

65%

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

The body is a thorough, highly actionable catalog of idiomatic Go patterns with real executable code and tooling config, but it is a long monolithic file that restates much standard Go knowledge Claude already has and lacks progressive disclosure into referenced detail files. It is strong on actionability and could improve on conciseness and file structure.

Suggestions

Trim or collapse sections that restate well-known Go fundamentals Claude already knows (e.g., the basic zero-value and accept-interfaces primers) to reduce token cost.

Split large reference material — the .golangci.yml config, the standard project layout, and the detailed pattern catalogs — into referenced files (e.g., references/tooling.md, references/project-layout.md) with one-level-deep links from SKILL.md.

For the toolchain section, add a light validation checkpoint (e.g., run `go vet`/`go test -race` before considering a change done) to give the reference a clearer workflow spine.

Dimension	Reasoning	Score
Conciseness	The prose is terse and code-dense, but the ~670-line body restates many well-known Go idioms (zero values, accept interfaces, error wrapping) that Claude already knows and could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	2 / 3
Actionability	It provides abundant real, executable Go code (worker pools, context handling, functional options, sync.Pool), concrete toolchain commands, and a copy-paste .golangci.yml config, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Content is well-organized into topical sections, but as a reference catalog it has no multi-step process sequence with validation checkpoints or feedback loops, matching the 'sequence present but checkpoints missing or implicit' level rather than a clear validated workflow.	2 / 3
Progressive Disclosure	The single SKILL.md is well-sectioned (not a disorganized wall of text), but at ~670 lines it is monolithic with no bundle files or one-level-deep references for content that could be split (linter config, project layout, detailed pattern catalogs), so it does not reach the 'clear overview with well-signaled references' anchor.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 clearly identifies the Go domain and purpose but stays abstract, listing categories (patterns, best practices, conventions) rather than concrete actions and omitting any explicit 'Use when…' trigger guidance. It is adequate but would benefit from concrete capabilities and natural trigger terms.

Suggestions

Add concrete actions to the description (e.g., 'Review, refactor, and structure Go code; handle errors, concurrency, and package layout') instead of the abstract 'patterns, best practices, conventions'.

Append an explicit 'Use when…' trigger clause with natural user phrasings (e.g., 'Use when writing, reviewing, or refactoring Go code, or designing Go packages and modules').

Include common natural keyword variations such as 'golang', 'Go code review', and 'Go refactoring' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Go domain and a broad action ('编写稳健、高效且易于维护的 Go 应用程序的惯用模式、最佳实践和约定'), but 'patterns, best practices, conventions' is abstract rather than a list of concrete actions, so it does not reach the 'multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly answers 'what' (idiomatic patterns/best practices/conventions for Go), but there is no 'Use when…' clause or equivalent explicit trigger in the description, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	It surfaces 'Go' / 'Go 应用程序' as a relevant keyword, but lacks common natural variations users would say (e.g., 'golang', 'Go code review', 'refactoring Go code'), matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The Go niche is fairly specific, but without explicit distinct trigger language it could still overlap with general code-review or code-pattern skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	8 / 12 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
skill_md_line_count	SKILL.md is long (675 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/golang-patterns/SKILL.md
Commit: dfbf946

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.