samber/oops Structured Errors
Structured error handling in Go with samber/oops — stack traces, codes, context
- What
- Structured error handling in Go with samber/oops — stack traces, codes, context
- Cost
- Free
- Needs
- a Go project with the Go toolchain installed; the samber/oops library as a dependency
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a guide to samber's own oops library (github.com/samber/oops): structured error handling for Go — error builders, stack traces, error codes, error context and attributes, error wrapping, user-facing vs developer messages, panic recovery, and logger integration. Variable data goes in .With() attributes (not the message string) so APM tools (Datadog, Loki, Sentry) can group errors properly, and attributes travel with the error through the call stack — unlike stdlib errors where you see "connection failed" without knowing which user triggered it. This is one of four library guides by @samber for his own Go libraries (alongside do for dependency injection, hot for in-memory caching, and ro for reactive streams) — self-promotional in subject, but substantial (282 lines) and genuinely useful when adopting the library. By @samber, listed here with credit to its creator. Honest caveats: requires a Go project importing samber/oops; it documents one specific library's API — not a general error-handling guide. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project with the Go toolchain installed; the samber/oops library as a dependency Install "samber/oops Structured Errors" for me. Structured error handling in Go with samber/oops — stack traces, codes, context Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-samber-oops/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-samber-oops skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-samber-oops". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.