Agent skill

Grpc Engineer

by FerroxLabs in FerroxLabs/wayland

Expert guide for designing and building gRPC services including protobuf schema design, streaming patterns, interceptors, error handling, load balancing, and performance optimization across polyglot…

Apache-2.0Auto-check passedBackend & APIs

Install Grpc Engineer

skills CLI
$ npx skills add FerroxLabs/wayland --skill grpc-engineer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland grpc-engineer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/backend-systems/grpc-engineer .claude/skills/grpc-engineer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
grpc-engineer
GitHub stars
608
Token cost
~3k tokens
SKILL.md length
332 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Expert guide for designing and building gRPC services including protobuf schema design, streaming patterns, interceptors, error handling, load balancing, and performance optimization across polyglot…

  • Works in 3 steps: Schema-first design - Define your .proto… → Backward compatibility - Never break… → Streaming when appropriate - Use unary…
  • The user asks about grpc engineer
  • SKILL.md covers Core Principles, Protobuf Schema Design, Service Definition and Streaming Patterns, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grpc Engineer is an agent skill from FerroxLabs/wayland. Expert guide for designing and building gRPC services including protobuf schema design, streaming patterns, interceptors, error handling, load balancing, and performance optimization across polyglot environments. Use when the user asks about grpc engineer, grpc engineer best practices, or needs guidance on grpc engineer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering gRPC and Protobuf. It works with gRPC. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about grpc engineer
  • Grpc engineer best practices
  • Needs guidance on grpc engineer implementation
  • The user needs a different specialized skill

Example prompts

  • “/grpc-engineer”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Schema-first design - Define your .proto files before writing any service code. The schema is the contract.
  2. Backward compatibility - Never break existing consumers. Follow protobuf evolution rules strictly.
  3. Streaming when appropriate - Use unary for simple request/response; streaming for real-time or large payloads.

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are go, protobuf, bash, yaml and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Grpc Engineer loads about 3k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 332 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 332 words, ~2,999 tokens.

Download SKILL.mdSave it as .claude/skills/grpc-engineer/SKILL.md (or your agent's skills folder).
name
grpc-engineer
description
Expert guide for designing and building gRPC services including protobuf schema design, streaming patterns, interceptors, error handling, load balancing, and performance optimization across polyglot environments. Use when the user asks about grpc engineer, grpc engineer best practices, or needs guidance on grpc engineer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
backend api-design guide
metadata.category
backend-systems
metadata.subcategory
api-design
metadata.disclaimer
none
metadata.difficulty
intermediate

gRPC Engineer

You are an expert in designing and building high-performance gRPC services. You guide teams through protobuf schema design, service definition, streaming patterns, interceptor middleware, error handling, and production deployment of gRPC-based systems.

Core Principles

  1. Schema-first design - Define your .proto files before writing any service code. The schema is the contract.
  2. Backward compatibility - Never break existing consumers. Follow protobuf evolution rules strictly.
  3. Streaming when appropriate - Use unary for simple request/response; streaming for real-time or large payloads.

Protobuf Schema Design

Message Best Practices
protobuf
syntax = "proto3";
package api.v1;

option go_package = "github.com/myorg/myapp/gen/api/v1;apiv1";

import "google/protobuf/timestamp.proto";
import "google/protobuf/field_mask.proto";
import "google/protobuf/wrappers.proto";

message User {
  // Field numbers 1-15 use 1 byte; reserve for frequently accessed fields
  string id = 1;
  string email = 2;
  string display_name = 3;
  UserRole role = 4;
  UserStatus status = 5;

  google.protobuf.Timestamp created_at = 10;
  google.protobuf.Timestamp updated_at = 11;
  google.protobuf.StringValue phone_number = 15;  // Nullable

  reserved 6, 8;
  reserved "legacy_name", "old_email";
}

enum UserRole {
  USER_ROLE_UNSPECIFIED = 0;    // Always have UNSPECIFIED as 0
  USER_ROLE_ADMIN = 1;
  USER_ROLE_EDITOR = 2;
  USER_ROLE_VIEWER = 3;
}
Field Evolution Rules
SAFE (backward compatible):
  - Add new fields with new field numbers
  - Add new enum values (not position 0)
  - Add new RPC methods or services

BREAKING (never do):
  - Remove/rename a field or change its number/type
  - Change enum value numbers
  - Remove an RPC method or rename a package

WHEN YOU MUST BREAK:
  - Create a new package version (api.v2)
  - Run both versions during migration

Service Definition

protobuf
service UserService {
  rpc CreateUser(CreateUserRequest) returns (CreateUserResponse);
  rpc GetUser(GetUserRequest) returns (GetUserResponse);
  rpc ListUsers(ListUsersRequest) returns (ListUsersResponse);
  rpc UpdateUser(UpdateUserRequest) returns (UpdateUserResponse);
  rpc DeleteUser(DeleteUserRequest) returns (DeleteUserResponse);
}

message ListUsersRequest {
  int32 page_size = 1;
  string page_token = 2;         // Opaque cursor
  string filter = 3;
  string order_by = 4;
}

message ListUsersResponse {
  repeated User users = 1;
  string next_page_token = 2;
  int32 total_count = 3;
}

message UpdateUserRequest {
  User user = 1;
  google.protobuf.FieldMask update_mask = 2;
}

Streaming Patterns

Pattern Decision Matrix
PATTERN               USE CASE                        EXAMPLE
---------------------------------------------------------------------
Unary                 Simple request/response         GetUser, CreateOrder
Server streaming      Server pushes multiple items    Subscribe, LargeExport
Client streaming      Client sends multiple items     FileUpload, BatchInsert
Bidirectional         Both sides push messages        Chat, LiveDashboard
Server Streaming (Go)
go
func (s *server) SubscribeEvents(req *pb.SubscribeRequest, stream pb.Service_SubscribeEventsServer) error {
    ch := s.eventBus.Subscribe(req.Topics)
    defer s.eventBus.Unsubscribe(ch)
    for {
        select {
        case event := <-ch:
            if err := stream.Send(event); err != nil {
                return status.Errorf(codes.Internal, "send failed: %v", err)
            }
        case <-stream.Context().Done():
            return nil
        }
    }
}
Client Streaming (Go)
go
func (s *server) UploadFile(stream pb.Service_UploadFileServer) error {
    var buf bytes.Buffer
    for {
        chunk, err := stream.Recv()
        if err == io.EOF {
            return stream.SendAndClose(&pb.UploadResponse{
                BytesReceived: int64(buf.Len()),
            })
        }
        if err != nil {
            return err
        }
        buf.Write(chunk.Data)
    }
}

Interceptors (Middleware)

Common Interceptor Stack
go
server := grpc.NewServer(
    grpc.ChainUnaryInterceptor(
        recoveryInterceptor,        // 1. Panic recovery (outermost)
        requestIDInterceptor,       // 2. Request ID injection
        loggingInterceptor,         // 3. Request/response logging
        metricsInterceptor,         // 4. Prometheus metrics
        authInterceptor,            // 5. Authentication
        validationInterceptor,      // 6. Request validation
    ),
    grpc.ChainStreamInterceptor(
        streamRecoveryInterceptor,
        streamLoggingInterceptor,
        streamAuthInterceptor,
    ),
)
Authentication Interceptor
go
func authInterceptor(
    ctx context.Context, req interface{},
    info *grpc.UnaryServerInfo, handler grpc.UnaryHandler,
) (interface{}, error) {
    if info.FullMethod == "/grpc.health.v1.Health/Check" {
        return handler(ctx, req)
    }
    md, ok := metadata.FromIncomingContext(ctx)
    if !ok {
        return nil, status.Error(codes.Unauthenticated, "missing metadata")
    }
    tokens := md.Get("authorization")
    if len(tokens) == 0 {
        return nil, status.Error(codes.Unauthenticated, "missing token")
    }
    claims, err := validateToken(tokens[0])
    if err != nil {
        return nil, status.Errorf(codes.Unauthenticated, "invalid token: %v", err)
    }
    ctx = context.WithValue(ctx, claimsKey, claims)
    return handler(ctx, req)
}

Error Handling

gRPC Status Codes
CODE                  WHEN TO USE
-----------------------------------------------------------
INVALID_ARGUMENT (3)  Client sent bad input (validation)
NOT_FOUND (5)         Resource does not exist
ALREADY_EXISTS (6)    Duplicate resource creation
PERMISSION_DENIED (7) Authenticated but not authorized
UNAUTHENTICATED (16)  Missing or invalid credentials
RESOURCE_EXHAUSTED (8) Rate limit or quota exceeded
FAILED_PRECONDITION (9) System not in required state
ABORTED (10)          Concurrency conflict (retry)
INTERNAL (13)         Internal server error
UNAVAILABLE (14)      Temporarily unavailable (retry)
Rich Error Details
go
func validateCreateUser(req *pb.CreateUserRequest) error {
    var violations []*errdetails.BadRequest_FieldViolation
    if req.Email == "" {
        violations = append(violations, &errdetails.BadRequest_FieldViolation{
            Field: "email", Description: "Email is required",
        })
    }
    if len(violations) > 0 {
        st := status.New(codes.InvalidArgument, "validation failed")
        detailed, _ := st.WithDetails(&errdetails.BadRequest{FieldViolations: violations})
        return detailed.Err()
    }
    return nil
}

Performance Optimization

Connection and Keepalive
go
conn, _ := grpc.Dial(target,
    grpc.WithTransportCredentials(creds),
    grpc.WithKeepaliveParams(keepalive.ClientParameters{
        Time: 10 * time.Second, Timeout: 3 * time.Second,
        PermitWithoutStream: true,
    }),
    grpc.WithDefaultCallOptions(
        grpc.MaxCallRecvMsgSize(10*1024*1024),
        grpc.MaxCallSendMsgSize(10*1024*1024),
    ),
)
Load Balancing
CLIENT-SIDE (service-to-service):
  round_robin, pick_first, or custom weighted
  conn, _ := grpc.Dial("dns:///service:50051",
      grpc.WithDefaultServiceConfig(`{"loadBalancingPolicy":"round_robin"}`))

PROXY-BASED (external clients):
  Envoy: full gRPC-aware L7 proxy
  Cloud LBs: GCP has native gRPC support

Code Generation with Buf

yaml
# buf.gen.yaml
version: v2
plugins:
  - remote: buf.build/protocolbuffers/go
    out: gen
    opt: paths=source_relative
  - remote: buf.build/grpc/go
    out: gen
    opt: paths=source_relative
shell
buf lint                                    # Lint protos
buf breaking --against '.git#branch=main'   # Check breaking changes
buf generate                                # Generate code

Health Checking and Reflection

go
import "google.golang.org/grpc/health"
import healthpb "google.golang.org/grpc/health/grpc_health_v1"

healthServer := health.NewServer()
healthpb.RegisterHealthServer(grpcServer, healthServer)
healthServer.SetServingStatus("api.v1.UserService", healthpb.HealthCheckResponse_SERVING)

// Reflection (dev/staging only)
reflection.Register(grpcServer)
shell
grpcurl -plaintext localhost:50051 list
grpcurl -plaintext -d '{"id":"user_123"}' localhost:50051 api.v1.UserService/GetUser

Production Checklist

SCHEMA:
  [ ] All enums have UNSPECIFIED = 0 value
  [ ] Reserved fields for any removed fields
  [ ] buf lint and breaking change detection in CI

SERVICE:
  [ ] Health check endpoint registered
  [ ] Interceptor chain: recovery > logging > metrics > auth > validation
  [ ] Deadlines propagated across service boundaries
  [ ] Graceful shutdown implemented

PERFORMANCE:
  [ ] Keepalive configured on client and server
  [ ] Max message size set appropriately
  [ ] Client-side load balancing configured

SECURITY:
  [ ] TLS enabled in production (never plaintext)
  [ ] Auth interceptor on all non-health RPCs
  [ ] Reflection disabled in production
  [ ] Input validation on all request messages

When to Use

Use this skill when:

  • Designing or implementing grpc engineer solutions
  • Reviewing or improving existing grpc engineer approaches
  • Making architectural or implementation decisions about grpc engineer
  • Learning grpc engineer patterns and best practices
  • Troubleshooting grpc engineer-related issues

Do NOT use this skill when:

  • The question is about a fundamentally different technology domain
  • A more specific sibling skill covers the exact topic needed
  • The user needs a complete hands-on tutorial rather than expert guidance

Output Format

markdown
# Grpc Engineer Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]

Example

Input: "Help me implement grpc engineer for a medium-scale production application"

Output: A structured analysis covering current state assessment, recommended grpc engineer approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.

Edge Cases

  • Legacy system integration: When grpc engineer must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
  • Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
  • Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
  • Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/backend-systems/grpc-engineer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Grpc Engineer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Grpc Engineer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grpc Engineer this skillFerroxLabs/wayland608—~3kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
Golang Proantoniopaya22/go-rest-template1723 repos~1.2kAutomated safety check: PassMIT
Debug Grpc ConnectionGetBindu/Bindu10k—~1.2kAutomated safety check: PassCustom licence
Aspnet Corefanslead/ReverseProxy.Store1632 repos~1.4kAutomated safety check: PassApache-2.0
Regenerate Grpc StubsGetBindu/Bindu10k—~810Automated safety check: PassCustom licence

Similar skills

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed
  • Golang Pro

    antoniopaya22/go-rest-template

    Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with…

    172 GitHub starsUsed in 3 repos~1.2k tokens
    Backend & APIsAuto-check passed
  • Debug Grpc Connection

    GetBindu/Bindu

    Diagnose gRPC connection issues between the Bindu core and a language SDK.

    10k GitHub stars~1.2k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Aspnet Core

    fanslead/ReverseProxy.Store

    Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development.

    163 GitHub starsUsed in 2 repos~1.4k tokens
    Backend & APIsAuto-check passed
  • Regenerate Grpc Stubs

    GetBindu/Bindu

    Regenerate Python + TypeScript gRPC stubs after editing proto files.

    10k GitHub stars~810 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Spider King

    aoyunyang/spider-king-skill

    Pure-web protocol reverse skill: turn hostile browser clients into browser-free Python collectors.

    507 GitHub stars~7.3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Grpc Engineer

What does Grpc Engineer do?

Expert guide for designing and building gRPC services including protobuf schema design, streaming patterns, interceptors, error handling, load balancing, and performance optimization across polyglot…. Grpc Engineer is an agent skill from FerroxLabs/wayland. Expert guide for designing and building gRPC services including protobuf schema design, streaming patterns, interceptors, error handling, load balancing, and performance optimization across polyglot environments.

When should I use Grpc Engineer?

Grpc Engineer fits situations like: the user asks about grpc engineer; grpc engineer best practices; needs guidance on grpc engineer implementation; the user needs a different specialized skill.

How do I install Grpc Engineer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill grpc-engineer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/backend-systems/grpc-engineer in FerroxLabs/wayland) into .claude/skills/grpc-engineer in your project. Claude Code loads it when a task matches its description.

How do I install Grpc Engineer in Codex?

Run `npx skills add FerroxLabs/wayland --skill grpc-engineer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/backend-systems/grpc-engineer in FerroxLabs/wayland) into .agents/skills/grpc-engineer in your project. Codex loads it when a task matches its description.

Can I use Grpc Engineer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill grpc-engineer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grpc-engineer, .gemini/skills/grpc-engineer, .github/skills/grpc-engineer and .opencode/skills/grpc-engineer in your project.

What does Grpc Engineer need to run?

SKILL.md names no scripts, command-line tools or credentials: Grpc Engineer is instructions for the agent only.

Does Grpc Engineer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Grpc Engineer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Grpc Engineer use?

Grpc Engineer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Grpc Engineer use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Grpc Engineer?

Skills that share tags, products or a category with Grpc Engineer: Use Yaak (mountain-loop/yaak, 19k stars), Golang Pro (antoniopaya22/go-rest-template, 172 stars), Debug Grpc Connection (GetBindu/Bindu, 10k stars) and Aspnet Core (fanslead/ReverseProxy.Store, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grpc Engineer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.