golang-patterns

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

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-CN/skills/golang-patterns/SKILL.md

Quality

Discovery

14%

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

This description is too vague and abstract, relying on buzzwords like 'robust, efficient, and maintainable' without specifying concrete actions or when the skill should be used. It lacks a 'Use when...' clause, specific trigger terms, and actionable capability descriptions that would help Claude distinguish it from other programming-related skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Go/Golang code patterns, error handling, concurrency, project structure, or idiomatic Go style.'

List specific concrete actions such as 'Reviews Go code for idiomatic patterns, suggests proper error handling, advises on goroutine/channel usage, recommends project layout conventions, and applies Go formatting standards.'

Include natural trigger terms users would say: 'golang', 'go code', 'goroutines', 'channels', 'go modules', 'go error handling', '.go files'.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like '惯用Go模式、最佳实践和约定' (idiomatic Go patterns, best practices, and conventions) without listing any concrete actions. Terms like 'robust, efficient, and maintainable' are buzzwords rather than specific capabilities.	1 / 3
Completeness	The description only vaguely addresses 'what' (idiomatic Go patterns and best practices) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	It includes 'Go' and '应用程序' (applications) which are relevant keywords, but misses common variations users might say like 'golang', 'go code review', 'go style', 'error handling', 'concurrency', or specific Go concepts.	2 / 3
Distinctiveness Conflict Risk	The description is very generic and could overlap with any Go-related skill, general coding best practices skill, or code review skill. There are no distinct triggers to differentiate it from other programming-related skills.	1 / 3
	Total	5 / 12 Passed

Implementation

57%

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

This is a comprehensive Go patterns reference with excellent, executable code examples covering error handling, concurrency, interfaces, and performance. However, it's overly verbose for Claude (who already knows idiomatic Go well), and the monolithic structure with no progressive disclosure makes it a poor fit for a SKILL.md that should be a concise overview pointing to detailed references. The content would benefit greatly from being split into a lean overview with links to topic-specific files.

Suggestions

Split the monolithic content into separate files (e.g., CONCURRENCY.md, ERROR_HANDLING.md, PERFORMANCE.md) and keep SKILL.md as a concise overview with links to each topic.

Remove patterns Claude already knows well (io.Reader/Writer interfaces, basic error wrapping, slice preallocation) and focus only on project-specific conventions or non-obvious patterns.

Add a brief workflow section for common tasks like 'adding a new endpoint' or 'refactoring a package' with sequenced steps and validation checkpoints (e.g., run tests, lint, vet).

Condense the quick reference table and anti-patterns section into the overview, as these are the highest-value-per-token sections.

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but verbose for Claude's level of knowledge. Many patterns shown (error handling, interfaces, slice preallocation, string building) are well-known Go idioms that Claude already understands deeply. The good/bad comparisons add value but the sheer volume (~400 lines) could be significantly condensed. Some sections like 'small focused interfaces' showing io.Reader/Writer are unnecessary.	2 / 3
Actionability	All code examples are fully executable and concrete. The skill provides copy-paste ready patterns for worker pools, graceful shutdown, functional options, error handling, and more. The tooling section includes specific CLI commands and a complete linter configuration file.	3 / 3
Workflow Clarity	The skill is primarily a pattern catalog rather than a workflow guide. While individual patterns are clear, there's no sequenced workflow for building a Go application or refactoring process. The 'when to activate' section lists triggers but doesn't guide through a decision process. For a patterns/best-practices skill this is acceptable, but the Go tooling section could benefit from a build-test-lint workflow with validation steps.	2 / 3
Progressive Disclosure	The entire skill is a monolithic document with no references to external files. At ~400 lines, sections like concurrency patterns, struct design, and performance could easily be split into separate reference files. There's no layered structure—everything is inline with no navigation aids beyond section headers.	1 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: affaan-m/everything-claude-code
Commit: 5df943e

Reviewed: about 22 hours 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.