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

85%

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

70%

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 Go patterns skill that leverages progressive disclosure effectively with verified reference files. Its main weakness is workflow clarity for multi-step/risky operations and minor conciseness redundancy between the summary list and the expanded sections.

Suggestions

Add an explicit sequence with a validation/checkpoint step for risky workflows (e.g. graceful shutdown and refactoring) rather than only listing review findings or delegating to sibling skills.

Reduce overlap between the 21-item Best Practices Summary and the expanded sections so each rule appears authoritatively once.

Tighten parenthetical explanations of basic Go semantics (zero values, string/byte conversions) since the target audience already knows them.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-and-rules content, but the 21-item Best Practices Summary restates several items that are then expanded again in later sections, and a few parenthetical asides (e.g. explaining zero-value behavior) add mild padding that could be tightened.	2 / 3
Actionability	Executable Go snippets (functional options Server, init avoidance, regexp compile, defer Close, context timeouts) plus concrete rules like 'start enums at 1' and 'compile regexp once at package level' give copy-paste-ready guidance.	3 / 3
Workflow Clarity	Design/Review modes are defined and review lists specific findings, but there is no explicit multi-step sequence with validation checkpoints for risky actions like refactors or graceful shutdown, and destructive refactor guidance is delegated out without an inline verify step.	2 / 3
Progressive Disclosure	SKILL.md is an overview with clearly signaled one-level-deep references to real files in references/ (architecture, clean-architecture, hexagonal-architecture, ddd, data-handling, resource-management) plus a Detailed Guides table and Cross-References section; navigation is easy and verified paths exist.	3 / 3
	Total	10 / 12 Passed

Description

100%

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, specific description that enumerates concrete capabilities and provides an explicit 'Apply when' trigger clause covering several natural scenarios. It is concise, uses third person, and is clearly distinguishable from sibling Go skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming) rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (catalog of Go design patterns) and 'when' via an explicit 'Apply when...' clause enumerating concrete triggering situations.	3 / 3
Trigger Term Quality	Natural user terms like 'functional options', 'constructors', 'graceful shutdown', 'resilience patterns', 'architectural patterns', and 'idiomatic Go pattern' are the phrases developers actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Go design-pattern selection with distinct triggers (functional options, graceful shutdown, architectural choice); unlikely to fire for non-Go or non-design skills.	3 / 3
	Total	12 / 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
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: 4158351

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