wolverine-grpc-handlers

Create Wolverine gRPC handlers for unary and server-streaming requests in .NET.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-grpc-handlers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wolverine-grpc-handlers
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/wolverine-grpc-handlers
Command: npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-grpc-handlers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Wolverine, Grpc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of creating robust and efficient gRPC handlers in .NET applications, leveraging Wolverine's gRPC features and the proto-first development model.

Core Features & Use Cases

  • Proto-first Development: Utilizes .proto files for service contracts and automatically generates C# classes.
  • Wolverine Integration: Seamlessly integrates with Wolverine's event-driven architecture for request handling and error handling.
  • Unary and Server-Streaming: Supports unary and server-streaming gRPC requests out of the box.
  • Middleware Support: Offers middleware for validation, before/after request processing, and exception handling.
  • Rich Error Details: Supports rich error details as per Google's AIP-193 for enhanced error communication.
  • Use Case: Build a ride-sharing platform where you can create gRPC services for dispatch, pricing, and telemetry with built-in validation, error handling, and robust request handling.

Quick Start

Author a gRPC handler using Wolverine by defining the .proto file for your service, creating a stub class with the [WolverineGrpcService] attribute, and implementing the handler logic in the handler's own file.

Frequently Asked Questions about wolverine-grpc-handlers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create gRPC handlers in .NET using a proto-first approach?

To create gRPC handlers with a proto-first approach, define your service contracts in .proto files to generate C# classes, then implement the handler logic using Wolverine's event-driven architecture for request routing.

Does Wolverine support server-streaming and unary gRPC requests?

Yes, Wolverine supports both unary and server-streaming gRPC requests out of the box, allowing you to handle standard request-response and continuous data stream operations within your .NET applications.

How do I add validation and error handling middleware to gRPC handlers?

You can add validation and error handling to gRPC handlers by applying Wolverine middleware, which supports before/after request processing, exception handling, and rich error details compliant with Google's AIP-193.

What is the proto-first development model for gRPC services?

The proto-first development model uses .proto files as the source of truth for your gRPC service contracts, automatically generating C# classes so you can focus on implementing the handler logic in separate files.

Can I use Wolverine's event-driven architecture for gRPC request handling?

Yes, Wolverine integrates its event-driven architecture directly with gRPC request handling, streamlining dispatch and error management while allowing handlers to be decorated with attributes like `[WolverineGrpcService]`.

How do gRPC handlers return rich error details in .NET?

gRPC handlers return rich error details by utilizing Wolverine's middleware to format exceptions and validation failures according to Google's AIP-193 standard, enhancing client-side error communication.