Name: golang-samber-oops
Rating: 68.8 (1 reviews)
Author: samber

golang-samber-oops

Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.

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

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 highly actionable, well-structured reference for samber/oops with executable examples and a clean one-level-deep advanced.md split. Weaknesses are mild intro redundancy and the absence of explicit validation checkpoints in its guidance.

Suggestions

De-duplicate the intro paragraph and the 'Why use samber/oops' bulleted list, which repeat the same feature set (structured context, stack traces, codes, public messages, low-cardinality).

Add an explicit validation or verification step where relevant — e.g., assert that wrapped errors carry expected attributes/tags, or show how to verify APM grouping in a quick check.

Consider moving the large builder-method table into advanced.md or a reference file so SKILL.md stays a leaner overview pointing to detail.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code and a tight builder-method table, but the intro paragraph and the 'Why use samber/oops' bulleted list overlap on the same feature set — a minor redundancy that could be trimmed.	4 / 5
Actionability	Copy-paste-ready Go examples cover the common cases — builder chain, repository/HTTP/service layers, wrapping, panic recovery, error access, output formats, and context propagation — with a detailed builder-method reference table.	5 / 5
Workflow Clarity	Clear DO/DON'T patterns and a layered wrapping sequence (Controller→Service→Repository) are present, but there are no explicit validation or verification checkpoints; guidance is pattern-oriented rather than a sequenced workflow.	3 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled one-level-deep reference to ./references/advanced.md (which exists and holds assertions, configuration, and logger examples); the inline builder-method table is sizable but is the core API reference.	4 / 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 capabilities and trigger conditions in third person, scoped tightly to samber/oops. The only gap is minor synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — 'error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration' — giving comprehensive coverage of the library's surface.	5 / 5
Completeness	Explicitly answers both 'what' (structured error handling capabilities) and 'when' ('Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('error handling', 'Golang', 'samber/oops', 'panic recovery', 'logger integration') plus the import path trigger, but lacks common synonyms like 'Go' (uses only 'Golang') and 'Go errors'.	4 / 5
Distinctiveness Conflict Risk	Scoped to a single named library with its import path as a trigger, giving a clear niche with minimal overlap risk against other skills.	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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

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