golang-design-patterns

Idiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming, and more. Apply when explicitly choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem.

Quality

84%

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

80%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, actionable patterns reference with executable Go examples and excellent progressive disclosure into real bundle files. Its main weakness is workflow clarity: the two modes are only loosely sequenced with no explicit validation or feedback checkpoints.

Suggestions

Tighten conciseness by trimming items in the Best Practices Summary that are fully re-explained in later sections (functional options, defer Close, regexp compilation), or compress the later sections to avoid restating the summary.

Strengthen workflow clarity by giving the Review mode an explicit validate-then-act checkpoint, e.g., 'run golangci-lint and report findings, then propose refactors only after the developer confirms priorities'.

For Design mode, add a concrete decision sequence (gather constraints → pick smallest sufficient pattern → show sketch → confirm before expanding) so the workflow has identifiable checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Go competence, but the 21-item Best Practices Summary restates several points later elaborated in their own sections (functional options, defer Close, compile regexp), creating minor duplication that could be trimmed.	4 / 5
Actionability	It provides multiple copy-paste-ready, executable Go snippets — functional-options Server, init() bad/good, enums, regexp.Mustlike compile, //go:embed, defer Close, context.WithTimeout — covering the common cases with real, complete code.	5 / 5
Workflow Clarity	The Design and Review modes give a light sequence (ask preference → propose smallest pattern; scan → report findings → suggest refactors), but there are no explicit validation checkpoints or feedback loops, and several topics defer entirely to other references.	3 / 5
Progressive Disclosure	SKILL.md is a clear overview with a well-signaled Detailed Guides table linking one level deep to real bundle files (architecture, clean-architecture, hexagonal-architecture, ddd, data-handling, resource-management), plus clearly marked cross-references to sibling skills — easy to navigate.	5 / 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.

A strong, third-person description that concretely catalogues its scope and pairs it with explicit, natural "Apply when" triggers. Minor overlap with sibling Go skills and a few missing synonyms keep it just short of perfect.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete pattern areas — "functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming" — giving comprehensive coverage of the skill's scope rather than vague language.	5 / 5
Completeness	It explicitly answers both "what" (the enumerated pattern catalog) and "when" via a concrete "Apply when ..." clause with multiple specific triggers, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like "implementing functional options", "designing constructor APIs", "setting up graceful shutdown", and "asking which idiomatic Go pattern fits a specific problem" match what a Go developer would say, though a few common synonyms (e.g., ".go" files, "Go idioms") are absent.	4 / 5
Distinctiveness Conflict Risk	"Idiomatic Golang design patterns" carves a clear niche, but the broad pattern catalog (error flow, context, data handling) overlaps with closely related sibling Go skills referenced in the body, leaving minor conflict risk.	4 / 5
	Total	18 / 20 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-design-patterns/SKILL.md
Commit: 30cdf15

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