Sanitize Go errors crossing trust boundaries with domain error types and slog redaction.
npx skills add https://github.com/nq-rdl/agent-extensions --skill go-secure-nq-rdl
Please help me install this Agent Skill. Skill: go-secure Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/go-secure Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill go-secure-nq-rdl
Secure Go error handling and information leakage prevention. Use whenever writing Go code that handles errors in APIs, services, or any code that crosses trust boundaries — HTTP handlers, gRPC services, CLI tools with user-facing output. Also trigger when reviewing Go error handling, implementing structured logging, or when the user mentions security, error sanitization, or preventing data leaks through error messages — even if they don't explicitly say "security". Covers domain error types, trust boundary translation, log redaction with slog, and safe API responses.
Apply secure Go error handling patterns to ensure errors crossing trust boundaries are translated and redacted before reaching clients.
High-intent search queries and answers about installing and using this skill.
To prevent data leakage in Go error messages, you should use domain error types that separate safe user messages from internal errors. This ensures implementation details are redacted before reaching clients in APIs or services.
Redact sensitive data in slog by applying contextual metadata allowlisting during structured logging. This prevents log bloat and leakage by filtering out sensitive information before it is written to your Go application logs.
Map Go domain errors to HTTP and gRPC statuses through trust boundary translation. This automatically converts internal DomainError types into appropriate user-visible HTTP handler or gRPC endpoint responses without leaking internal stack traces.
Sanitize CLI tool output by applying trust boundary translation and opaque wrapping to Go errors. This prevents exposing internal implementation details by ensuring only safe, redacted messages are displayed to the user in CLI tools.
You need opaque wrapping for Go error handling when errors cross trust boundaries like HTTP handlers or gRPC endpoints. It prevents leaking implementation details by hiding internal error structures from user-visible API responses.
JylhisEnforce idiomatic Go error handling with wrapping, inspection, and structured logging.
javierhbrImplement Go HTTP middleware for context propagation, slog logging, and panic recovery.
sigitpoerwoBuild scalable backend architectures with strict input validation and transactional integrity.
TheBushidoCollectiveImplement Go error handling with wrapping, unwrapping, and sentinel errors.
