Implement Go gRPC services with error handling, health checks, and interceptors.
npx skills add https://github.com/omarluq/og-template --skill golang-grpc-omarluq
Please help me install this Agent Skill. Skill: golang-grpc Source: https://github.com/omarluq/og-template/tree/main/.agents/skills/golang-grpc Command: npx skills add https://github.com/omarluq/og-template --skill golang-grpc-omarluq
Go gRPC services require a cohesive pattern to ensure correct error handling, health checks, and maintainable code. This skill consolidates best practices for building, reviewing, and debugging Go gRPC servers and clients, organizing protobufs, and setting up testing with bufconn.
Start by structuring your Go gRPC service with health checks, interceptors, and UnimplementedServer embedding, then progressively add TLS, testing, and robust error handling.
High-intent search queries and answers about installing and using this skill.
Configure Go gRPC services by adding health checks, wrapping calls with interceptors, embedding Unimplemented*Server for forward compatibility, and mapping errors to status codes. This structure separates business logic and ensures maintainable production-grade servers.
The best way to test gRPC services in Go is using bufconn. This pattern allows you to test servers and clients, including streaming RPCs, without relying on actual network ports, ensuring reliable and isolated test execution for production-grade systems.
TLS and mTLS configuration secures client-server communication by requiring certificate exchange. This skill provides guidance on setting up mutual TLS to ensure encrypted, authenticated connections within your production-grade gRPC infrastructure.
You need to embed Unimplemented*Server in Go gRPC services to maintain forward compatibility. It ensures your service remains compilable and operational when new RPC methods are added to protobuf definitions but not yet implemented in the server.
Handle error mapping in gRPC by translating application-level errors into standard gRPC status codes. This skill enforces proper error handling patterns, allowing clients to programmatically react to specific failure types like invalid arguments or internal errors.
Yes, you can use interceptors in gRPC for clean separation of business logic. Interceptors allow you to wrap RPC calls to handle cross-cutting concerns like logging or authentication, keeping core service methods focused on business rules.
333-333-333Define protobuf contracts and generate Go gRPC stubs for microservices.
timequityAutomate containerized deployments using Docker and CI/CD pipelines.
hung-phanConfigure LiteLLM with connection pooling, caching, and OpenTelemetry tracing.
moonmingConfigure Apache APISIX grpc-transcode plugin for HTTP and gRPC protocol conversion.
