Golang Samber Oops

v1.1.2

Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facin...

0· 95·0 current·0 all-time
bySamuel Berthe@samber
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name, description, and content focus on structured error handling with samber/oops; the only declared runtime dependency is the Go binary, which is appropriate for Go code examples and guidance.
Instruction Scope
SKILL.md contains examples, patterns, and guidance specific to samber/oops; it does not instruct the agent to read unrelated files, collect system secrets, or transmit data to external endpoints beyond normal documentation references.
Install Mechanism
There is no install spec and no code files to write or execute — this is an instruction-only skill, which minimizes install-time risk.
Credentials
The skill requests no environment variables or credentials. The guidance and examples do not require secrets or unrelated credentials.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modification of other skills/config; autonomous invocation is allowed by platform default but the skill itself is instruction-only and not asking for elevated privileges.
Assessment
This skill is an instructional guide for using the samber/oops Go library (no code is installed and no credentials are requested). Before enabling it, verify you have Go on PATH and that your project actually uses github.com/samber/oops (or you intend to adopt it). Also review the examples to ensure they match your error-handling policies and coding standards. Note: the SKILL.md declares allowed tools (shell/git/linting) as typical agent capabilities — the skill's instructions themselves don't perform shell/file operations, but if your agent runs skills autonomously, consider whether you want to permit those tool operations platform-wide.

Like a lobster shell, security has layers — review code before you run it.

latestvk972494ke7mbpk4gz03aq9wd41842fwt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

💥 Clawdis
Binsgo

Comments