golang-idioms

Idiomatic Go patterns for error handling, interfaces, concurrency, testing, and module management

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/golang-idioms/SKILL.md

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent lean, actionable Go pattern reference with executable code and real commands, scoring top marks for conciseness and actionability. It loses points only because it is a monolithic multi-topic reference with no sequenced workflow/validation checkpoints and no progressive disclosure into separate reference files.

Suggestions

Split detailed material (e.g. full concurrency patterns, testing helpers) into reference files under references/ and link to them from a concise overview to improve progressive disclosure.

For operations that carry risk if done wrong (e.g. dependency updates, goroutine lifecycle), add an explicit validate/check step (e.g. 'run go build ./... and go test ./... before committing after go get -u ./...') to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout: each section is a compact code example followed by terse 'Rules:' bullets, with no padding explaining what Go is or how libraries work, so every token earns its place and it assumes Claude's competence.	3 / 3
Actionability	It provides fully executable, copy-paste-ready Go code (e.g. the worker pool, fan-out, table-driven test, slog usage) plus concrete commands ('go mod tidy', 'go mod verify', 'go list -m -u all'), matching the executable-and-specific anchor.	3 / 3
Workflow Clarity	Content is organized into clearly headed sections, but this is a multi-topic pattern reference rather than a sequenced workflow; there are no explicit validation checkpoints or feedback loops, and the under-50-line single-purpose exception does not apply to this ~300-line reference.	2 / 3
Progressive Disclosure	Sections are well-organized by topic, but everything is inlined in a single ~300-line SKILL.md with no references/ or other bundle files, so detail that could be split out (e.g. advanced concurrency patterns, testing helpers) is not progressively disclosed.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 is third-person, on-topic, and clearly Go-specific, but it enumerates topic areas rather than concrete actions and lacks an explicit 'Use when ...' trigger clause, which caps both specificity and completeness at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or reviewing Go code, refactoring Go for idiomatic style, or when the user mentions Go best practices, goroutines, interfaces, or error handling.'

Lead with concrete actions rather than topic labels, e.g. 'Write, refactor, and review Go code using idiomatic patterns for ...' to reach the multiple-concrete-actions anchor.

Include natural variations users say (goroutines, channels, Go best practices, Go patterns) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Idiomatic Go patterns") and several topics ("error handling, interfaces, concurrency, testing, and module management"), but these are topic labels rather than concrete actions like "extract" or "fill", so it stops short of the level-3 multiple-concrete-actions anchor.	2 / 3
Completeness	It states what the skill covers ("Idiomatic Go patterns for ...") but provides no "Use when ..." clause or equivalent explicit trigger guidance, so the when is missing rather than explicit, capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Natural terms a user would say appear ("Go", "error handling", "concurrency", "testing"), but common variations such as "best practices", "goroutines", "channels", and "Go patterns" are absent, matching the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	The phrase is scoped specifically to Go idioms, a clear niche with distinct triggers that is unlikely to conflict with non-Go skills, matching the clear-niche anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: rohitg00/awesome-claude-code-toolkit
Path: skills/golang-idioms/SKILL.md
Commit: ebdf1d5

Reviewed: 2 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.