[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFP7NEHT51YP1577RHVYA0":3,"skill-same:01M7DFP7NEHT51YP1577RHVYA0":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":60},"01M7DFP7NEHT51YP1577RHVYA0","golang-samber-oops",null,"Structured error handling in Golang with samber\u002Foops — 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\u002Foops, or when the codebase already imports github.com\u002Fsamber\u002Foops.","heynemann\u002Fomp-marketplace","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7DFBDAM3NXF540P210W3NYT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fgolang-samber-oops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-samber-oops\ndescription: \"Structured error handling in Golang with samber\u002Foops — 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\u002Foops, or when the codebase already imports github.com\u002Fsamber\u002Foops.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.2.1\"\n  openclaw:\n    emoji: \"💥\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\n    skill-library-version: \"1.21.0\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*\npaths:\n  - \"**\u002F*.go\"\n---\n\n**Persona:** You are a Go engineer who treats errors as structured data. Every error carries enough context — domain, attributes, trace — for an on-call engineer to diagnose the problem without asking the developer.\n\n# samber\u002Foops Structured Error Handling\n\n**samber\u002Foops** is a drop-in replacement for Go's standard error handling that adds structured context, stack traces, error codes, public messages, and panic recovery. Variable data goes in `.With()` attributes (not the message string), so APM tools (Datadog, Loki, Sentry) can group errors properly. Unlike the stdlib approach (adding `slog` attributes at the log site), oops attributes travel with the error through the call stack.\n\n## Why use samber\u002Foops\n\nStandard Go errors lack context — you see `connection failed` but not which user triggered it, what query was running, or the full call stack. `samber\u002Foops` provides:\n\n- **Structured context** — key-value attributes on any error\n- **Stack traces** — automatic call stack capture\n- **Error codes** — machine-readable identifiers\n- **Public messages** — user-safe messages separate from technical details\n- **Low-cardinality messages** — variable data in `.With()` attributes, not the message string, so APM tools group errors properly\n\nThis skill is not exhaustive — refer to library documentation and code examples for more information:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n## Core pattern: Error builder chain\n\nAll `oops` errors use a fluent builder pattern:\n\n```go\nerr := oops.\n    In(\"user-service\").           \u002F\u002F domain\u002Ffeature\n    Tags(\"database\", \"postgres\").  \u002F\u002F categorization\n    Code(\"network_failure\").       \u002F\u002F machine-readable identifier\n    User(\"user-123\", \"email\", \"foo@bar.com\").  \u002F\u002F user context\n    With(\"query\", query).          \u002F\u002F custom attributes\n    Errorf(\"failed to fetch user: %s\", \"timeout\")\n```\n\nTerminal methods:\n\n- `.Errorf(format, args...)` — create a new error\n- `.Wrap(err)` — wrap an existing error\n- `.Wrapf(err, format, args...)` — wrap with a message\n- `.Join(err1, err2, ...)` — combine multiple errors\n- `.Recover(fn)` \u002F `.Recoverf(fn, format, args...)` — convert panic to error\n\n### Error builder methods\n\n| Methods | Use case |\n| --- | --- |\n| `.With(\"key\", value)` | Add custom key-value attribute (lazy `func() any` values supported) |\n| `.WithContext(ctx, \"key1\", \"key2\")` | Extract values from Go context into attributes (lazy values supported) |\n| `.In(\"domain\")` | Set the feature\u002Fservice\u002Fdomain |\n| `.Tags(\"auth\", \"sql\")` | Add categorization tags (query with `err.HasTag(\"tag\")`) |\n| `.Code(\"iam_authz_missing_permission\")` | Set machine-readable error identifier\u002Fslug |\n| `.Public(\"Could not fetch user.\")` | Set user-safe message (separate from technical details) |\n| `.Hint(\"Runbook: https:\u002F\u002Fdoc.acme.org\u002Fdoc\u002Fabcd.md\")` | Add debugging hint for developers |\n| `.Owner(\"team\u002Fslack\")` | Identify responsible team\u002Fowner |\n| `.User(id, \"k\", \"v\")` | Add user identifier and attributes |\n| `.Tenant(id, \"k\", \"v\")` | Add tenant\u002Forganization context and attributes |\n| `.Trace(id)` | Add trace \u002F correlation ID (default: ULID) |\n| `.Span(id)` | Add span ID representing a unit of work\u002Foperation (default: ULID) |\n| `.Time(t)` | Override error timestamp (default: `time.Now()`) |\n| `.Since(t)` | Set duration based on time since `t` (exposed via `err.Duration()`) |\n| `.Duration(d)` | Set explicit error duration |\n| `.Request(req, includeBody)` | Attach `*http.Request` (optionally including body) |\n| `.Response(res, includeBody)` | Attach `*http.Response` (optionally including body) |\n| `oops.FromContext(ctx)` | Start from an `OopsErrorBuilder` stored in a Go context |\n\n## Common scenarios\n\n### Database\u002Frepository layer\n\n```go\nfunc (r *UserRepository) FetchUser(id string) (*User, error) {\n    query := \"SELECT * FROM users WHERE id = $1\"\n    row, err := r.db.Query(query, id)\n    if err != nil {\n        return nil, oops.\n            In(\"user-repository\").\n            Tags(\"database\", \"postgres\").\n            With(\"query\", query).\n            With(\"user_id\", id).\n            Wrapf(err, \"failed to fetch user from database\")\n    }\n    \u002F\u002F ...\n}\n```\n\n### HTTP handler layer\n\n```go\nfunc (h *Handler) CreateUser(w http.ResponseWriter, r *http.Request) {\n    userID := getUserID(r)\n\n    err := h.service.CreateUser(r.Context(), userID)\n    if err != nil {\n        err = oops.\n            In(\"http-handler\").\n            Tags(\"endpoint\", \"\u002Fusers\").\n            Request(r, false).\n            User(userID).\n            Wrapf(err, \"create user failed\")\n        http.Error(w, oops.GetPublic(err, \"Internal server error\"), http.StatusInternalServerError)\n        return\n    }\n\n    w.WriteHeader(http.StatusCreated)\n}\n```\n\n### Service layer with reusable builder\n\n```go\nfunc (s *UserService) CreateOrder(ctx context.Context, req CreateOrderRequest) error {\n    builder := oops.\n        In(\"order-service\").\n        Tags(\"orders\", \"checkout\").\n        Tenant(req.TenantID, \"plan\", req.Plan).\n        User(req.UserID, \"email\", req.UserEmail)\n\n    product, err := s.catalog.GetProduct(ctx, req.ProductID)\n    if err != nil {\n        return builder.\n            With(\"product_id\", req.ProductID).\n            Wrapf(err, \"product lookup failed\")\n    }\n\n    if product.Stock \u003C req.Quantity {\n        return builder.\n            Code(\"insufficient_stock\").\n            Public(\"Not enough items in stock.\").\n            With(\"requested\", req.Quantity).\n            With(\"available\", product.Stock).\n            Errorf(\"insufficient stock for product %s\", req.ProductID)\n    }\n\n    return nil\n}\n```\n\n## Error wrapping best practices\n\n### DO: Wrap directly, no nil check needed\n\n```go\n\u002F\u002F ✓ Good — Wrap returns nil if err is nil\nreturn oops.Wrapf(err, \"operation failed\")\n\n\u002F\u002F ✗ Bad — unnecessary nil check\nif err != nil {\n    return oops.Wrapf(err, \"operation failed\")\n}\nreturn nil\n```\n\n### DO: Add context at each layer\n\nEach architectural layer SHOULD add context via Wrap\u002FWrapf — at least once per package boundary (not necessarily at every function call).\n\n```go\n\u002F\u002F ✓ Good — each layer adds relevant context\nfunc Controller() error {\n    return oops.In(\"controller\").Trace(traceID).Wrapf(Service(), \"user request failed\")\n}\n\nfunc Service() error {\n    return oops.In(\"service\").With(\"op\", \"create_user\").Wrapf(Repository(), \"db operation failed\")\n}\n\nfunc Repository() error {\n    return oops.In(\"repository\").Tags(\"database\", \"postgres\").Errorf(\"connection timeout\")\n}\n```\n\n### DO: Keep error messages low-cardinality\n\nError messages MUST be low-cardinality for APM aggregation. Interpolating variable data into the message breaks grouping in Datadog, Loki, Sentry.\n\n```go\n\u002F\u002F ✗ Bad — high-cardinality, breaks APM grouping\noops.Errorf(\"failed to process user %s in tenant %s\", userID, tenantID)\n\n\u002F\u002F ✓ Good — static message + structured attributes\noops.With(\"user_id\", userID).With(\"tenant_id\", tenantID).Errorf(\"failed to process user\")\n```\n\n## Panic recovery\n\n`oops.Recover()` MUST be used in goroutine boundaries. Convert panics to structured errors:\n\n```go\nfunc ProcessData(data string) (err error) {\n    return oops.\n        In(\"data-processor\").\n        Code(\"panic_recovered\").\n        Hint(\"Check input data format and dependencies\").\n        With(\"input_data\", data).\n        Recover(func() {\n            riskyOperation(data)\n        })\n}\n```\n\n## Accessing error information\n\n`samber\u002Foops` errors implement the standard `error` interface. Access additional info:\n\n```go\nif oopsErr, ok := err.(oops.OopsError); ok {\n    fmt.Println(\"Code:\", oopsErr.Code())\n    fmt.Println(\"Domain:\", oopsErr.Domain())\n    fmt.Println(\"Tags:\", oopsErr.Tags())\n    fmt.Println(\"Context:\", oopsErr.Context())\n    fmt.Println(\"Stacktrace:\", oopsErr.Stacktrace())\n}\n\n\u002F\u002F Get public-facing message with fallback\npublicMsg := oops.GetPublic(err, \"Something went wrong\")\n```\n\n### Output formats\n\n```go\nfmt.Printf(\"%+v\\n\", err)       \u002F\u002F verbose with stack trace\nbytes, _ := json.Marshal(err)  \u002F\u002F JSON for logging\nslog.Error(err.Error(), slog.Any(\"error\", err))  \u002F\u002F slog integration\n```\n\n## Context propagation\n\nCarry error context through Go contexts:\n\n```go\nfunc middleware(next http.Handler) http.Handler {\n    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n        builder := oops.\n            In(\"http\").\n            Request(r, false).\n            Trace(r.Header.Get(\"X-Trace-ID\"))\n\n        ctx := oops.WithBuilder(r.Context(), builder)\n        next.ServeHTTP(w, r.WithContext(ctx))\n    })\n}\n\nfunc handler(ctx context.Context) error {\n    return oops.FromContext(ctx).Tags(\"handler\", \"users\").Errorf(\"something failed\")\n}\n```\n\nFor assertions, configuration, and additional logger examples, see [Advanced patterns](.\u002Freferences\u002Fadvanced.md).\n\n## References\n\n- [github.com\u002Fsamber\u002Foops](https:\u002F\u002Fgithub.com\u002Fsamber\u002Foops)\n- [pkg.go.dev\u002Fgithub.com\u002Fsamber\u002Foops](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fsamber\u002Foops)\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-error-handling` skill for general error handling patterns\n- → See `samber\u002Fcc-skills-golang@golang-observability` skill for logger integration and structured logging\n","**Persona:** You are a Go engineer who treats errors as structured data. Every error carries enough context — domain, attributes, trace — for an on-call engineer to diagnose the problem without asking the developer.\n\n# samber\u002Foops Structured Error Handling\n\n**samber\u002Foops** is a drop-in replacement for Go's standard error handling that adds structured context, stack traces, error codes, public messages, and panic recovery. Variable data goes in `.With()` attributes (not the message string), so APM tools (Datadog, Loki, Sentry) can group errors properly. Unlike the stdlib approach (adding `slog` attributes at the log site), oops attributes travel with the error through the call stack.\n\n## Why use samber\u002Foops\n\nStandard Go errors lack context — you see `connection failed` but not which user triggered it, what query was running, or the full call stack. `samber\u002Foops` provides:\n\n- **Structured context** — key-value attributes on any error\n- **Stack traces** — automatic call stack capture\n- **Error codes** — machine-readable identifiers\n- **Public messages** — user-safe messages separate from technical details\n- **Low-cardinality messages** — variable data in `.With()` attributes, not the message string, so APM tools group errors properly\n\nThis skill is not exhaustive — refer to library documentation and code examples for more information:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n## Core pattern: Error builder chain\n\nAll `oops` errors use a fluent builder pattern:\n\n```go\nerr := oops.\n    In(\"user-service\").           \u002F\u002F domain\u002Ffeature\n    Tags(\"database\", \"postgres\").  \u002F\u002F categorization\n    Code(\"network_failure\").       \u002F\u002F machine-readable identifier\n    User(\"user-123\", \"email\", \"foo@bar.com\").  \u002F\u002F user context\n    With(\"query\", query).          \u002F\u002F custom attributes\n    Errorf(\"failed to fetch user: %s\", \"timeout\")\n```\n\nTerminal methods:\n\n- `.Errorf(format, args...)` — create a new error\n- `.Wrap(err)` — wrap an existing error\n- `.Wrapf(err, format, args...)` — wrap with a message\n- `.Join(err1, err2, ...)` — combine multiple errors\n- `.Recover(fn)` \u002F `.Recoverf(fn, format, args...)` — convert panic to error\n\n### Error builder methods\n\n| Methods | Use case |\n| --- | --- |\n| `.With(\"key\", value)` | Add custom key-value attribute (lazy `func() any` values supported) |\n| `.WithContext(ctx, \"key1\", \"key2\")` | Extract values from Go context into attributes (lazy values supported) |\n| `.In(\"domain\")` | Set the feature\u002Fservice\u002Fdomain |\n| `.Tags(\"auth\", \"sql\")` | Add categorization tags (query with `err.HasTag(\"tag\")`) |\n| `.Code(\"iam_authz_missing_permission\")` | Set machine-readable error identifier\u002Fslug |\n| `.Public(\"Could not fetch user.\")` | Set user-safe message (separate from technical details) |\n| `.Hint(\"Runbook: https:\u002F\u002Fdoc.acme.org\u002Fdoc\u002Fabcd.md\")` | Add debugging hint for developers |\n| `.Owner(\"team\u002Fslack\")` | Identify responsible team\u002Fowner |\n| `.User(id, \"k\", \"v\")` | Add user identifier and attributes |\n| `.Tenant(id, \"k\", \"v\")` | Add tenant\u002Forganization context and attributes |\n| `.Trace(id)` | Add trace \u002F correlation ID (default: ULID) |\n| `.Span(id)` | Add span ID representing a unit of work\u002Foperation (default: ULID) |\n| `.Time(t)` | Override error timestamp (default: `time.Now()`) |\n| `.Since(t)` | Set duration based on time since `t` (exposed via `err.Duration()`) |\n| `.Duration(d)` | Set explicit error duration |\n| `.Request(req, includeBody)` | Attach `*http.Request` (optionally including body) |\n| `.Response(res, includeBody)` | Attach `*http.Response` (optionally including body) |\n| `oops.FromContext(ctx)` | Start from an `OopsErrorBuilder` stored in a Go context |\n\n## Common scenarios\n\n### Database\u002Frepository layer\n\n```go\nfunc (r *UserRepository) FetchUser(id string) (*User, error) {\n    query := \"SELECT * FROM users WHERE id = $1\"\n    row, err := r.db.Query(query, id)\n    if err != nil {\n        return nil, oops.\n            In(\"user-repository\").\n            Tags(\"database\", \"postgres\").\n            With(\"query\", query).\n            With(\"user_id\", id).\n            Wrapf(err, \"failed to fetch user from database\")\n    }\n    \u002F\u002F ...\n}\n```\n\n### HTTP handler layer\n\n```go\nfunc (h *Handler) CreateUser(w http.ResponseWriter, r *http.Request) {\n    userID := getUserID(r)\n\n    err := h.service.CreateUser(r.Context(), userID)\n    if err != nil {\n        err = oops.\n            In(\"http-handler\").\n            Tags(\"endpoint\", \"\u002Fusers\").\n            Request(r, false).\n            User(userID).\n            Wrapf(err, \"create user failed\")\n        http.Error(w, oops.GetPublic(err, \"Internal server error\"), http.StatusInternalServerError)\n        return\n    }\n\n    w.WriteHeader(http.StatusCreated)\n}\n```\n\n### Service layer with reusable builder\n\n```go\nfunc (s *UserService) CreateOrder(ctx context.Context, req CreateOrderRequest) error {\n    builder := oops.\n        In(\"order-service\").\n        Tags(\"orders\", \"checkout\").\n        Tenant(req.TenantID, \"plan\", req.Plan).\n        User(req.UserID, \"email\", req.UserEmail)\n\n    product, err := s.catalog.GetProduct(ctx, req.ProductID)\n    if err != nil {\n        return builder.\n            With(\"product_id\", req.ProductID).\n            Wrapf(err, \"product lookup failed\")\n    }\n\n    if product.Stock \u003C req.Quantity {\n        return builder.\n            Code(\"insufficient_stock\").\n            Public(\"Not enough items in stock.\").\n            With(\"requested\", req.Quantity).\n            With(\"available\", product.Stock).\n            Errorf(\"insufficient stock for product %s\", req.ProductID)\n    }\n\n    return nil\n}\n```\n\n## Error wrapping best practices\n\n### DO: Wrap directly, no nil check needed\n\n```go\n\u002F\u002F ✓ Good — Wrap returns nil if err is nil\nreturn oops.Wrapf(err, \"operation failed\")\n\n\u002F\u002F ✗ Bad — unnecessary nil check\nif err != nil {\n    return oops.Wrapf(err, \"operation failed\")\n}\nreturn nil\n```\n\n### DO: Add context at each layer\n\nEach architectural layer SHOULD add context via Wrap\u002FWrapf — at least once per package boundary (not necessarily at every function call).\n\n```go\n\u002F\u002F ✓ Good — each layer adds relevant context\nfunc Controller() error {\n    return oops.In(\"controller\").Trace(traceID).Wrapf(Service(), \"user request failed\")\n}\n\nfunc Service() error {\n    return oops.In(\"service\").With(\"op\", \"create_user\").Wrapf(Repository(), \"db operation failed\")\n}\n\nfunc Repository() error {\n    return oops.In(\"repository\").Tags(\"database\", \"postgres\").Errorf(\"connection timeout\")\n}\n```\n\n### DO: Keep error messages low-cardinality\n\nError messages MUST be low-cardinality for APM aggregation. Interpolating variable data into the message breaks grouping in Datadog, Loki, Sentry.\n\n```go\n\u002F\u002F ✗ Bad — high-cardinality, breaks APM grouping\noops.Errorf(\"failed to process user %s in tenant %s\", userID, tenantID)\n\n\u002F\u002F ✓ Good — static message + structured attributes\noops.With(\"user_id\", userID).With(\"tenant_id\", tenantID).Errorf(\"failed to process user\")\n```\n\n## Panic recovery\n\n`oops.Recover()` MUST be used in goroutine boundaries. Convert panics to structured errors:\n\n```go\nfunc ProcessData(data string) (err error) {\n    return oops.\n        In(\"data-processor\").\n        Code(\"panic_recovered\").\n        Hint(\"Check input data format and dependencies\").\n        With(\"input_data\", data).\n        Recover(func() {\n            riskyOperation(data)\n        })\n}\n```\n\n## Accessing error information\n\n`samber\u002Foops` errors implement the standard `error` interface. Access additional info:\n\n```go\nif oopsErr, ok := err.(oops.OopsError); ok {\n    fmt.Println(\"Code:\", oopsErr.Code())\n    fmt.Println(\"Domain:\", oopsErr.Domain())\n    fmt.Println(\"Tags:\", oopsErr.Tags())\n    fmt.Println(\"Context:\", oopsErr.Context())\n    fmt.Println(\"Stacktrace:\", oopsErr.Stacktrace())\n}\n\n\u002F\u002F Get public-facing message with fallback\npublicMsg := oops.GetPublic(err, \"Something went wrong\")\n```\n\n### Output formats\n\n```go\nfmt.Printf(\"%+v\\n\", err)       \u002F\u002F verbose with stack trace\nbytes, _ := json.Marshal(err)  \u002F\u002F JSON for logging\nslog.Error(err.Error(), slog.Any(\"error\", err))  \u002F\u002F slog integration\n```\n\n## Context propagation\n\nCarry error context through Go contexts:\n\n```go\nfunc middleware(next http.Handler) http.Handler {\n    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n        builder := oops.\n            In(\"http\").\n            Request(r, false).\n            Trace(r.Header.Get(\"X-Trace-ID\"))\n\n        ctx := oops.WithBuilder(r.Context(), builder)\n        next.ServeHTTP(w, r.WithContext(ctx))\n    })\n}\n\nfunc handler(ctx context.Context) error {\n    return oops.FromContext(ctx).Tags(\"handler\", \"users\").Errorf(\"something failed\")\n}\n```\n\nFor assertions, configuration, and additional logger examples, see [Advanced patterns](.\u002Freferences\u002Fadvanced.md).\n\n## References\n\n- [github.com\u002Fsamber\u002Foops](https:\u002F\u002Fgithub.com\u002Fsamber\u002Foops)\n- [pkg.go.dev\u002Fgithub.com\u002Fsamber\u002Foops](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fsamber\u002Foops)\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-error-handling` skill for general error handling patterns\n- → See `samber\u002Fcc-skills-golang@golang-observability` skill for logger integration and structured logging\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":37,"compatibility":38,"user-invocable":39},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.2.1",{"emoji":30,"install":31,"homepage":32,"requires":33,"skill-library-version":36},"💥",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":34},[35],"go","1.21.0","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*","Designed for Claude Code, Codex or similar harness, and for projects using Golang.",true,"main","2147d79c9cd764770418b462c29634bcdc710096","plugins\u002Fbase\u002Fskills\u002Fgolang-samber-oops","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-09-29 21:26:05",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":39},[50,53,56],{"tool":51,"command":52},"npx","npx skills add heynemann\u002Fomp-marketplace --skill golang-samber-oops",{"tool":54,"command":55},"bunx","bunx skills add heynemann\u002Fomp-marketplace --skill golang-samber-oops",{"tool":57,"command":58},"pnpm","pnpm dlx skills add heynemann\u002Fomp-marketplace --skill golang-samber-oops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fgolang-samber-oops\u002FSKILL.md",[61,67],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"evals\u002Fevals.json","REFERENCE","参考文档",13037,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fgolang-samber-oops\u002Fevals\u002Fevals.json",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fadvanced.md",1347,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fgolang-samber-oops\u002Freferences\u002Fadvanced.md",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DFXDYP0N6P8KR0AF7C0TDK","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DFX9C5B0T1T0AVDCWNR5P2","write-skill","Use when creating, designing, or fixing an agent skill (SKILL.md pack) — triggers include \"write a skill\", \"make me a skill\", \"create a skill\", skill directories, and skills that fail to trigger or fire on the wrong tasks.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DFX64VSTQV0CSGYR76MPZF","write-agent","Use when creating, designing, or fixing an omp subagent (task agent) — triggers include \"write an agent\", \"make me an agent\", \"create a subagent\", agent `.md` definitions, and agents that misbehave when spawned via task.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwrite-agent\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DFX22JEY7ZN9EDESM732K5","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7DFWYXR5V2CY2BPDAAS19R1","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7DFWXFFMBKV294WS66S475V","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[]]