Name: golang-error-handling
Rating: 67.2 (1 reviews)
Author: samber

golang-error-handling

Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.

Quality

82%

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

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

Well-structured overview that delegates detail to real, clearly-signaled reference files and gives specific API-level guidance. The main gap is the absence of explicit validation/feedback checkpoints for its batch audit workflows, and no inline executable code examples.

Suggestions

Add an explicit validation/consolidation step after the parallel audit sub-agents run (e.g., dedupe findings, re-verify each violation against the source, confirm the rule applies) so the batch workflow has a feedback loop and can score higher on workflow clarity.

Include one or two short inline executable code snippets in the body (e.g., a canonical fmt.Errorf wrapping example and an errors.Is check) so core guidance is copy-paste ready without opening a reference file.

Trim the Cross-References section or fold it into the detailed-reference descriptions to remove restated sibling-skill pointers already present in the description and summary.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — a numbered summary, brief reference descriptions, and links — and does not explain concepts Claude already knows, though the Cross-References section and summary restate sibling-skill and rule details already covered, adding minor redundancy.	4 / 5
Actionability	Concrete, specific guidance names exact APIs (fmt.Errorf with %w, errors.Is/As/AsType[T], errors.Join, slog) and concrete audit targets, but the body itself contains no executable code examples, relying on the reference files for worked examples.	4 / 5
Workflow Clarity	Audit and review modes give a named sequence (5 sub-agents, sequential review steps), but the skill drives batch codebase operations with no explicit validation/dedupe/re-check feedback loop, which the rubric caps at 3 for batch operations.	3 / 5
Progressive Disclosure	A clear overview with a well-signaled Detailed Reference section linking three real one-level-deep bundle files (./references/error-creation.md, error-wrapping.md, error-handling.md), each with a concise description, making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

92%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, specific description that clearly states both what the skill covers and when to use it, with comprehensive capability enumeration and good delegation to sibling skills for overlap areas. Slightly technical in its trigger terms but highly actionable.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers 'what' via the long capability list and 'when' via the trigger clause 'Apply when creating, wrapping, inspecting, or logging errors in Go code', matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('error handling', 'creating, wrapping, inspecting, or logging errors', 'Go') plus specific API names, but leans technical and omits some common lay synonyms, so not a full 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Go error handling) with distinct triggers and explicitly hands overlapping concerns (samber/oops, slog) to sibling skills, minimizing conflict risk.	5 / 5
	Total	19 / 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_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-error-handling/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.