Go Middleware
v2.3.0Idiomatic Go HTTP middleware patterns with context propagation, structured logging via slog, centralized error handling, and panic recovery. Use when writing...
⭐ 0· 110·1 current·1 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is a documentation/reference pack for idiomatic Go HTTP middleware (context propagation, slog logging, error handling, recovery). It requests no binaries, env vars, or installs and the included guidance/code examples align with the stated purpose.
Instruction Scope
SKILL.md and reference files contain code examples and patterns limited to middleware concerns (request IDs, context helpers, logging, error mapping, recovery). Examples reference outgoing HTTP calls and DB calls only as illustrations for propagating context/cancellation — which is coherent for middleware guidance. There are no instructions to read system files, harvest environment variables, or transmit telemetry to unexpected external endpoints.
Install Mechanism
No install spec and no code files to execute. This is instruction-only documentation so nothing is downloaded or written to disk by an installer.
Credentials
The skill declares no required environment variables, credentials, or config paths. The examples mention standard runtime concerns (e.g., selecting a logger handler based on env) but do not require or request secrets or unrelated credentials.
Persistence & Privilege
always:false and no mechanisms to persist or modify agent/system configuration. The skill is user-invocable and can be called by the agent (normal for skills) but it does not request elevated or permanent privileges.
Assessment
This skill is a documentation/reference pack (examples you can copy into your code). It does not install anything or ask for credentials. Before using the examples, ensure your project uses a compatible Go version (slog is Go 1.21+), add any needed Go module dependencies (uuid package, etc.), and review handlers for accidental logging of sensitive data (tokens, passwords). Pay attention to the suggested ordering (Recovery should be outermost) and to implementing optional ResponseWriter interfaces in the statusWriter if you need Flush/Hijack/Pusher support. Because this is just guidance, there is no runtime risk from the skill itself — but when you copy examples into production code, review them for context-appropriate security (avoid logging secrets, ensure error details are not leaked to clients, and validate any downstream requests).Like a lobster shell, security has layers — review code before you run it.
latestvk97dsfatyn36n9t944d0v1srg983czra
License
MIT-0
Free to use, modify, and redistribute. No attribution required.