golang-patterns

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

Quality

43%

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-TW/skills/golang-patterns/SKILL.md

Quality

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 explain what concrete actions Claude performs or when this skill should be selected over others. The absence of explicit trigger guidance and concrete capabilities makes it difficult for Claude to reliably choose this skill.

Suggestions

Add specific concrete actions like 'Reviews Go code for idiomatic patterns, suggests error handling improvements, generates struct definitions, and refactors functions for better concurrency'

Include a 'Use when...' clause with trigger terms such as 'Use when working with Go/golang code, .go files, or when the user asks about goroutines, channels, interfaces, or Go error handling'

Add common keyword variations users might say: 'golang', '.go', 'goroutines', 'channels', 'Go modules', 'go fmt'

Dimension	Reasoning	Score
Specificity	The description uses abstract language like 'idiomatic patterns', 'best practices', and 'conventions' without listing any concrete actions. It doesn't specify what Claude actually does (e.g., 'reviews code', 'suggests refactoring', 'generates Go code').	1 / 3
Completeness	The description only vaguely addresses 'what' (patterns and practices) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	Contains 'Go' and 'Go applications' which are relevant keywords users might say, but misses common variations like 'golang', '.go files', or specific Go concepts users might mention (goroutines, channels, error handling).	2 / 3
Distinctiveness Conflict Risk	While 'Go' provides some specificity, the generic terms 'best practices', 'patterns', and 'conventions' could overlap with any language-specific coding skill. It's not clearly distinguished from general code review or other programming skills.	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 actionable code examples showing good/bad comparisons. The main weaknesses are verbosity (some explanatory text Claude doesn't need) and the monolithic structure that could benefit from progressive disclosure to separate files. The content is well-organized but optimized more for human learning than for efficient Claude context usage.

Suggestions

Remove explanatory prose that describes concepts Claude already knows (e.g., 'Go prefers simplicity over cleverness', 'Design types so their zero value is useful') - the code examples already demonstrate these principles

Split into multiple files: keep SKILL.md as a concise overview with links to CONCURRENCY.md, PERFORMANCE.md, ERROR_HANDLING.md for detailed patterns

Add a brief 'When to use' context at the top of each major section to help Claude quickly identify which pattern applies to the current task

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some explanatory text that Claude already knows (e.g., explaining what zero values are, basic Go concepts). Some sections could be tightened, though the code examples are generally efficient.	2 / 3
Actionability	Excellent executable code examples throughout - all patterns show complete, copy-paste ready Go code with clear good/bad comparisons. The bash commands and linter config are directly usable.	3 / 3
Workflow Clarity	This is primarily a patterns/reference skill rather than a multi-step workflow skill. The patterns are clear but lack explicit validation checkpoints or feedback loops for when to apply each pattern during development.	2 / 3
Progressive Disclosure	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 referenced files.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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: 18 days 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.