golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
Install with Tessl CLI
npx tessl i github:ysyecust/everything-claude-code --skill golang-patterns53
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description is too abstract and lacks actionable specificity. It reads more like a tagline than a functional skill description, failing to enumerate concrete capabilities or provide explicit trigger conditions for when Claude should select this skill.
Suggestions
Add a 'Use when...' clause with specific triggers like 'Use when writing Go/Golang code, reviewing Go projects, or when the user asks about Go idioms, error handling, concurrency patterns, or Go project structure'
Replace abstract terms with concrete actions such as 'Write idiomatic Go code, implement error handling patterns, structure Go projects, use goroutines and channels correctly, apply Go naming conventions'
Include common user terms and file extensions: 'Golang', '.go files', 'go modules', 'go.mod', 'goroutines', 'channels'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language like 'idiomatic patterns', 'best practices', and 'conventions' without listing any concrete actions. It describes qualities (robust, efficient, maintainable) rather than specific capabilities Claude can perform. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (Go patterns/practices) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Includes 'Go' and 'Go applications' which users would naturally say, but lacks common variations like 'Golang', 'golang code', or specific Go concepts users might mention (goroutines, channels, error handling, etc.). | 2 / 3 |
Distinctiveness Conflict Risk | While it specifies Go as the language, 'best practices' and 'patterns' are generic enough to potentially conflict with other coding or architecture skills. The lack of specific Go-related triggers reduces distinctiveness. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid Go patterns reference with excellent, executable code examples covering core idioms, error handling, concurrency, and performance. The main weaknesses are its length (could be split into focused sub-documents) and some unnecessary explanatory prose that Claude doesn't need. The anti-patterns section and quick reference table are particularly valuable.
Suggestions
Split into multiple files: core patterns in SKILL.md, with separate CONCURRENCY.md, PERFORMANCE.md, and TOOLING.md files linked from the main document
Remove explanatory sentences like 'Go favors simplicity over cleverness' - the code examples demonstrate this without needing to state it
Add a brief 'When to use which pattern' decision tree or flowchart to improve workflow clarity for pattern selection
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory text that Claude already knows (e.g., 'Go favors simplicity over cleverness'). The examples are good but could be tighter in places, and some patterns like the standard project layout could be more condensed. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all patterns include complete, copy-paste ready Go code. The tooling section provides specific commands, and the linter configuration is directly usable. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for applying these patterns. The skill is more of a reference than a step-by-step guide. For a patterns/best-practices skill this is acceptable, but validation checkpoints for when to apply which pattern are missing. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (concurrency, performance) into separate files with clear navigation. | 2 / 3 |
Total | 9 / 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 | |
- 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.