golang-patterns
用于构建健壮、高效且可维护的Go应用程序的惯用Go模式、最佳实践和约定。
37
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. It reads more like a tagline than a functional skill description that Claude could use to disambiguate among multiple skills.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Go/Golang coding patterns, error handling, package structure, concurrency, or idiomatic Go style.'
List specific concrete actions the skill covers, such as 'Guides error handling patterns, struct/interface design, package organization, goroutine management, and testing conventions in Go.'
Include natural trigger terms users would say, such as 'golang', 'Go code review', 'Go project structure', 'goroutines', 'channels', '.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 'structure packages', 'handle errors', 'write tests', or 'manage concurrency'. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (idiomatic Go patterns and best practices) and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | It includes 'Go' and '应用程序' (applications) as relevant keywords, but misses many natural trigger terms users would say like 'golang', 'error handling', 'goroutines', 'interfaces', 'structs', 'packages', or specific Go concepts. | 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 high-quality, executable Go code examples covering a broad range of idiomatic patterns, but it suffers from being overly comprehensive and monolithic. Much of the content covers patterns Claude already knows well (basic error handling, string building, slice preallocation), and the entire document could be condensed to a focused overview with references to detailed sub-files. The actionability is excellent but undermined by the volume of content competing for context window space.
Suggestions
Split the monolithic content into separate reference files (e.g., ERRORS.md, CONCURRENCY.md, INTERFACES.md, PERFORMANCE.md) and keep SKILL.md as a concise overview with links to each.
Remove explanations of patterns Claude already knows well (basic error handling, strings.Builder vs concatenation, slice preallocation) and focus on project-specific conventions or non-obvious patterns.
Add a brief decision framework or flowchart for when to apply specific patterns (e.g., when to use errgroup vs WaitGroup, when functional options are warranted vs simple constructors).
Trim the 'When to activate' section—it's generic enough to be omitted entirely, as Claude can infer when Go patterns apply.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose for its audience. Many patterns shown (error handling, interfaces, zero values) are well-known Go idioms that Claude already understands. The good/bad comparisons add value but the sheer volume (~400 lines) covering basics like 'don't ignore errors' and 'use strings.Builder' is unnecessary for Claude. | 2 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready. The examples cover real patterns with complete function signatures, proper imports, and realistic usage scenarios. The tooling section provides exact CLI commands. | 3 / 3 |
Workflow Clarity | This is a pattern/convention skill rather than a multi-step workflow skill, so explicit validation checkpoints are less critical. However, the skill lacks any guidance on when to apply which pattern, or a decision tree for choosing between approaches. The 'When to activate' section is generic and doesn't help sequence actions. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. At ~400 lines covering error handling, concurrency, interfaces, package organization, struct design, performance, and tooling, this would benefit greatly from splitting into focused reference files with a concise overview in SKILL.md. | 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
928076c
- 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.