If you're tired of Go errors that just say "connection failed" with zero context about which user, which query, or where in the stack it broke, this skill teaches Claude to use samber/oops for structured error handling. It wraps errors with key-value attributes, stack traces, error codes, and user-safe messages. The big win is keeping variable data out of error strings and in `.With()` attributes instead, so your APM tools can actually group errors properly. Good for any Go project where you need to debug production issues without Slacking the original author at 2am.
npx skills add https://github.com/samber/cc-skills-golang --skill golang-samber-oops