golang-patterns

用于构建健壮、高效且可维护的Go应用程序的惯用Go模式、最佳实践和约定。

Quality

66%

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

Quality

Content

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

The body is a highly actionable, well-organized catalog of idiomatic Go patterns with extensive executable code and tooling guidance. Its main weaknesses are the absence of an explicit validated workflow and a monolithic single-file structure with no progressive disclosure to separate reference files.

Suggestions

Add a short 'Workflow' section with explicit validation checkpoints (e.g. write → gofmt → go vet → go test -race → golangci-lint, re-run on failure).

Split the large reference material (full .golangci.yml config and the detailed pattern/anti-pattern catalogs) into one-level-deep files under references/ and link to them from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient: each section is a brief one-line description followed by concrete code, with little padding; not a 5 because some prose restates concepts Claude already knows (e.g. 'Go 推崇简洁而非精巧') and the closing '记住' line is mildly fluffy.	4 / 5
Actionability	Packed with complete, copy-paste-ready functions (error wrapping, worker pools, errgroup, functional options, sync.Pool) plus concrete tooling commands and a full .golangci.yml, covering the common Go cases comprehensively.	5 / 5
Workflow Clarity	Content is organized by topic with a '何时激活' section, but there is no explicit multi-step workflow with validation checkpoints or error-recovery feedback loops; the anchors for a clear sequenced process are not met, and no destructive/batch workflow exists to cap the score lower.	3 / 5
Progressive Disclosure	Good in-document section structure (headers, quick-reference table, anti-patterns), but the ~670-line SKILL.md is monolithic with no bundle files and no one-level-deep references; content that belongs in separate reference files (full linter config, detailed pattern catalogs) is inlined, so the 'overview pointing to detailed materials' ideal is only partially met.	3 / 5
	Total	15 / 20 Passed

Description

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

The description clearly identifies a Go-specific niche and uses reasonable trigger terms, but it omits any explicit 'Use when...' activation guidance and relies on abstract category labels (patterns, best practices, conventions) rather than concrete enumerated actions. These two gaps cap completeness and specificity.

Suggestions

Add an explicit activation clause, e.g. 'Use when writing, reviewing, refactoring, or designing Go code.'

Replace the abstract category list with a few concrete actions, e.g. 'Idiomatic Go patterns, error handling, concurrency, and package design for building robust, efficient, maintainable Go applications.'

Include natural trigger variations such as '.go files' or 'Golang' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the Go domain and conveys categories of actions ("惯用Go模式、最佳实践和约定" for "构建...Go应用程序"), but these are abstract category labels rather than concrete specific actions, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor; not a 4 because no specific individual patterns are enumerated.	3 / 5
Completeness	Provides a clear 'what' (idiomatic Go patterns, best practices, conventions for robust/efficient/maintainable Go apps) but no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("Go应用程序", "惯用Go模式", "最佳实践", "约定") with good coverage; not a 5 because common variations like ".go 文件" or "Golang" are absent.	4 / 5
Distinctiveness Conflict Risk	Clearly Go-specific niche with distinct triggers, so minimal conflict risk; not a 5 because the description lacks explicit trigger phrases that would fully disambiguate it from a general code-review or generic Go skill.	4 / 5
	Total	14 / 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
skill_md_line_count	SKILL.md is long (676 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: affaan-m/ECC
Path: docs/zh-CN/skills/golang-patterns/SKILL.md
Commit: e04ea0b

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.