golang-patterns

Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.

Quality

81%

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

Quality

Content

76%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.

A well-structured, highly actionable Go patterns reference with executable code throughout. Its main weakness is the absence of any selection/application workflow or validation guidance, and all content living inline rather than progressively disclosed.

Suggestions

Add a short 'How to choose' or decision guide (e.g., when to use functional options vs. constructors, when to use sentinel vs. custom errors) to give the catalog a sequenced selection workflow and lift workflow_clarity.

Trim the opening blockquote and the generic 'Benefits:' bullet lists, which restate knowledge Claude already has, to tighten conciseness.

Move the longer reference material (e.g., full package-organization layout, testing helpers) into one-level-deep reference files linked from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	A lean, code-first reference that assumes Claude's competence and avoids explaining basic Go concepts; minor padding remains in the opening blockquote and the repetitive "Benefits:" bullet lists, keeping it just below the 5 anchor.	4 / 5
Actionability	Every section ships complete, copy-paste-ready Go code covering the common cases (functional options, worker pool, context propagation, error wrapping, table-driven tests), matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced workflow; individual patterns are clear, but there are no multi-step processes, validation checkpoints, or guidance on selecting and combining patterns, so it does not rise above the 3 anchor.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but ~215 lines of content are all inlined with no split into one-level-deep reference files, a minor organization gap versus the 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

87%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.

A strong, third-person description that clearly states capability scope and an explicit use-when trigger. Minor gains are available from adding natural synonyms (golang, .go extensions) and leading with action verbs.

Dimension	Reasoning	Score
Specificity	Lists six concrete Go pattern areas ("functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization"), which is comprehensive coverage, but they are framed as pattern categories rather than action verbs, so it sits just below the 5 anchor.	4 / 5
Completeness	Explicitly answers both what (the enumerated Go patterns) and when ("Use when working with Go code to apply idiomatic Go patterns") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ("working with Go code", "idiomatic Go patterns"), but omits common synonyms and file extensions like "golang" and ".go" that the 5 anchor expects.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to Go ("Go-specific design patterns") with distinct language-specific triggers and matching globs, giving it a clear niche with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/golang-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.