Golang Samber Slog
v1.0.3Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute form...
⭐ 0· 103·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description focus on samber/slog libraries and the skill only requires the Go binary and provides code examples and references — these are proportionate and expected for a Go logging guidance skill.
Instruction Scope
SKILL.md contains concrete Go code examples, pipeline patterns, and references to handler constructors and shutdown semantics; it does not instruct reading unrelated files, exfiltrating data, or using unrelated environment variables or system paths.
Install Mechanism
No install spec and no code files to execute — instruction-only skills have minimal disk/write risk. Examples reference public import paths (github.com/samber/...) rather than downloads from unknown servers.
Credentials
The skill requests no environment variables or credentials. It shows examples that mention webhooks/tokens for backends (expected) but does not require them itself.
Persistence & Privilege
always:false and no install actions. The skill does not request permanent presence or modify other skills/configs. Autonomous invocation is allowed by default but there are no other red flags that amplify risk.
Assessment
This is a documentation-only skill describing how to compose samber/slog Go logging pipelines — it appears coherent and low-risk. Before using in production: (1) review and pin the actual library versions you import (the skill references v2/v3 in places), (2) provide backend credentials (Datadog, Sentry, Slack, Loki, webhook URLs) only to your application and keep them secret, (3) follow the guidance to flush/Stop batched handlers during graceful shutdown to avoid lost logs, and (4) validate PII scrubbing and sampling rules in staging so you don’t accidentally drop errors or leak sensitive data. If you want extra assurance, inspect the upstream repositories (github.com/samber/...) referenced in the docs before embedding these handlers in your codebase.Like a lobster shell, security has layers — review code before you run it.
latestvk975ycpgwzex9qen64w3krjgyn843vb2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🪵 Clawdis
Binsgo