go-best-practices

Provides Go patterns for type-first development with custom types, interfaces, functional options, and error handling. Must use when reading or writing Go files.

1.10x

Quality

85%

Does it follow best practices?

Impact

91%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

The body is well-organized, assumes Go competence, and provides extensive executable examples with a clear type-first workflow. Slight verbosity in glosses and inline encyclopedic code that could be split into reference files keep it just below the top anchors.

Suggestions

Trim restatement-of-the-obvious glosses (e.g. "Panics crash the program", "Runaway requests cause cascading failures") that Claude already knows.

Move the longer worked examples (e.g. the full LoadConfig and iota enum blocks) into a reference file and link to it, keeping SKILL.md as an overview to improve progressive disclosure.

Add an explicit validate/recover loop for the error-handling and exhaustive-switch guidance (e.g. "run go vet/build, fix reported cases, repeat") to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Go knowledge, with terse annotations, but a few trailing glosses like "Runaway requests cause cascading failures" and "Panics crash the program" restate what Claude already knows.	4 / 5
Actionability	Multiple complete, copy-paste-ready snippets (functional options, slog logging, LoadConfig, iota enums) cover the common cases; only a few illustrative stubs like "// implementation" keep it from being a concern.	5 / 5
Workflow Clarity	The Type-First Development section gives a clear four-step numbered sequence, but the Instructions section is a bullet list without an explicit validate-and-recover feedback loop, leaving minor checkpoint gaps.	4 / 5
Progressive Disclosure	No bundle directories exist, so the skill is self-contained with clear section headers and no nested references; the encyclopedic inlining of many code patterns that could live in reference files is a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

88%Weight 40%Scale 1-5

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 specific, complete, and clearly distinct as a Go best-practices skill with an explicit use-when clause. Minor gaps in trigger synonyms and a somewhat broad file-type trigger keep trigger quality and distinctiveness just below the top anchor.

Suggestions

Add natural synonyms and the file extension to the trigger, e.g. "Use when reading, writing, or reviewing Go (.go) files or Golang code."

Tighten the verb from "Provides Go patterns" to concrete actions like "Apply type-first Go patterns..." to match the most specific anchor phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — "custom types, interfaces, functional options, and error handling" — comparable in coverage to the anchor-5 example, though "Provides Go patterns" is a slightly more abstract verb than extract/fill/merge.	5 / 5
Completeness	Explicitly answers both what (Go patterns for type-first development with four named areas) and when ("Must use when reading or writing Go files"), matching the concrete-trigger-phrases anchor.	5 / 5
Trigger Term Quality	"reading or writing Go files" and "type-first," "functional options," "error handling" are natural terms a user would say, but synonyms like "Golang" and the ".go" extension are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear Go niche with a file-type trigger, but "reading or writing Go files" is broad enough to overlap with other Go-related skills, so it sits just below the minimal-conflict anchor.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/go-best-practices/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours 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.