golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
51
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-TW/skills/golang-patterns/SKILL.mdQuality
Discovery
22%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 reads more like a tagline than a functional skill description. It lacks concrete actions, explicit trigger conditions, and sufficient specificity to distinguish it from other Go-related skills. The vague language ('best practices', 'conventions') provides little guidance for Claude to determine when to select this skill over alternatives.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Go coding style, idiomatic Go, error handling patterns, struct design, or interface usage.'
Replace vague terms like 'best practices and conventions' with specific concrete actions, e.g., 'Reviews Go code for idiomatic style, suggests proper error handling with wrapped errors, applies interface segregation, and structures packages following standard Go project layout.'
Include common trigger terms users would naturally say, such as 'golang', '.go files', 'goroutines', 'channels', 'error wrapping', 'Go modules', to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'idiomatic patterns', 'best practices', and 'conventions' without listing any concrete actions. It doesn't specify what the skill actually does (e.g., 'reviews code for idiomatic style', 'refactors functions to use Go conventions', 'generates Go structs with proper tags'). | 1 / 3 |
Completeness | The description weakly addresses 'what' (Go patterns and best practices) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 2, and the 'what' is itself too vague to earn a 2. | 1 / 3 |
Trigger Term Quality | It includes 'Go' and 'Go applications' which are relevant keywords users might use, but misses common variations like 'golang', '.go files', 'goroutines', 'error handling', 'interfaces', or other specific Go concepts users would naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | While it specifies Go as the language, the broad scope of 'patterns, best practices, and conventions' could overlap with any Go-related skill such as Go testing, Go code review, or Go project setup. It lacks a clear niche. | 2 / 3 |
Total | 6 / 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 best-practices reference with excellent, executable code examples covering error handling, concurrency, interfaces, and performance. However, it's overly long for a single SKILL.md file—it would benefit significantly from splitting detailed sections into separate files and keeping the main file as a concise overview. Some explanatory prose could be trimmed since Claude already understands Go fundamentals.
Suggestions
Split detailed sections (concurrency patterns, interface design, performance, anti-patterns) into separate referenced files and keep SKILL.md as a concise overview with links to each topic.
Remove explanatory prose that restates Go fundamentals Claude already knows (e.g., 'Go prefers simplicity over cleverness', 'Design types so their zero value is immediately usable without initialization')—let the code examples speak for themselves.
Add a workflow section with sequenced steps for common tasks like 'setting up a new Go project' or 'reviewing Go code' with explicit validation checkpoints (e.g., run tests, run linters, verify).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary commentary that Claude already knows (e.g., 'Go prefers simplicity over cleverness', explaining what zero values are). The good/bad pattern comparisons are useful but some explanatory text could be trimmed. The Chinese comments add some overhead but serve as section headers. | 2 / 3 |
Actionability | Every pattern is illustrated with fully executable, copy-paste-ready Go code examples. The code covers concrete scenarios (worker pools, graceful shutdown, error wrapping, functional options) with both good and bad examples, plus tool commands are specific and runnable. | 3 / 3 |
Workflow Clarity | This is primarily a patterns/best-practices reference rather than a multi-step workflow skill. The tooling section lists commands but doesn't sequence them into a workflow with validation checkpoints. For a skill that includes build/test/lint operations, explicit sequencing with validation steps would improve clarity. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text at ~400+ lines with no references to external files for detailed topics. Sections like concurrency patterns, interface design, and performance could be split into separate reference files with the SKILL.md serving as a concise overview with links. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (674 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- haniakrim21/everything-claude-code
- Commit
ae2cadd
- 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.