golang-patterns
用于构建健壮、高效且可维护的Go应用程序的惯用Go模式、最佳实践和约定。
47
36%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-CN/skills/golang-patterns/SKILL.mdQuality
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 to be effective for skill selection. It lacks concrete actions, explicit trigger conditions, and distinctive keywords that would help Claude choose it from a pool of skills. It reads more like a tagline than a functional skill description.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Go/Golang coding patterns, error handling, concurrency, project structure, or idiomatic Go style.'
List specific concrete actions the skill performs, such as 'Reviews Go code for idiomatic patterns, suggests proper error handling with wrapped errors, advises on goroutine and channel usage, recommends package structure and naming conventions.'
Include natural trigger terms users would say, such as 'golang', 'go code', 'goroutines', 'channels', 'go modules', 'go project structure', '.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 such as 'format code', 'write tests', 'handle errors', or 'structure packages'. | 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 '应用程序' (application) as relevant keywords, but misses common natural trigger terms users would say like 'golang', 'go code review', 'error handling', 'concurrency', 'goroutines', or specific Go idioms. | 2 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'best practices and conventions' could overlap with any Go-related skill, coding standards skill, or general programming guidance skill. There are no distinct triggers to differentiate it. | 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 skill provides comprehensive, well-structured Go patterns with excellent executable code examples and good/bad comparisons. However, it is significantly too long for a SKILL.md, covering many patterns Claude already knows well, and would benefit from aggressive trimming and splitting into referenced sub-files. The lack of progressive disclosure and the breadth of 'known' Go conventions being re-taught are its main weaknesses.
Suggestions
Split the monolithic content into separate reference files (e.g., CONCURRENCY.md, ERROR_HANDLING.md, INTERFACES.md) and keep SKILL.md as a concise overview with links to each topic.
Remove or drastically reduce sections covering standard Go knowledge Claude already has (basic error handling, interface composition, slice preallocation) and focus on project-specific conventions or non-obvious patterns.
Add a brief development workflow section with validation checkpoints: write code → go vet → go test -race → golangci-lint run → commit.
Trim the quick reference table and anti-patterns section, which largely repeat advice already given in the code examples above them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400 lines) and covers many Go patterns that Claude already knows well (error handling, interfaces, concurrency). While the examples are useful, much of this is standard Go knowledge that doesn't need to be taught. The 'Core Principles' section explaining simplicity and zero values is largely redundant for Claude. However, it avoids truly egregious padding and stays focused on code examples rather than prose explanations. | 2 / 3 |
Actionability | Every section includes complete, executable Go code examples with clear good/bad comparisons. The code is copy-paste ready, includes concrete commands (go test, go vet, etc.), and provides a complete .golangci.yml configuration. The project layout is specific and actionable. | 3 / 3 |
Workflow Clarity | This is primarily a patterns/conventions skill rather than a multi-step workflow skill, so explicit sequential workflows are less critical. However, the skill lacks any validation checkpoints or feedback loops — for example, there's no guidance on 'write code → run go vet → fix issues → run tests → verify' as a development workflow. The content is organized by topic but doesn't sequence steps for applying these patterns. | 2 / 3 |
Progressive Disclosure | This is a monolithic ~400-line file with no references to external files or any structural layering. The content covers error handling, concurrency, interfaces, package organization, struct design, performance, tooling, and anti-patterns all inline. This would benefit greatly from splitting into separate reference files (e.g., CONCURRENCY.md, ERROR_HANDLING.md) with a concise overview in the main skill. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%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
841beea
- 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.