agentsclimarketplace

Protobuf grpc designer

Skill a5c-ai/babysitter/library/specializations/sdk-platform-development/skills/protobuf-grpc-designer

Protocol Buffers and gRPC service definition with backward compatibility checksFrom its SKILL.md

Install
npx -y skills add a5c-ai/babysitter --skill protobuf-grpc-designer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.4 KB, 395 tokens by cl100k_base, as published. Nobody here has run it

Protocol Buffers and gRPC Designer Skill

Overview

This skill specializes in designing Protocol Buffers schemas and gRPC service definitions with a focus on backward compatibility, performance, and cross-language interoperability.

Capabilities

  • Design .proto files following Google's style guide and best practices
  • Implement gRPC service definitions with streaming support
  • Validate wire format backward compatibility
  • Generate language-specific stubs for multiple targets
  • Configure proto linting and breaking change detection
  • Design efficient message structures for performance
  • Implement gRPC interceptors and middleware patterns

Target Processes

  • API Design Specification
  • Backward Compatibility Management
  • Multi-Language SDK Strategy

Integration Points

  • buf (schema registry, linting, breaking change detection)
  • protoc (Protocol Buffer compiler)
  • grpcurl (gRPC testing)
  • gRPC-Gateway (REST transcoding)
  • Connect (modern gRPC alternative)

Input Requirements

  • Service domain requirements
  • Message structure definitions
  • Streaming requirements (unary, server, client, bidirectional)
  • Target languages for code generation
  • Backward compatibility policy

Output Artifacts

  • .proto schema files
  • buf.yaml configuration
  • Generated language stubs
  • Breaking change analysis report
  • API documentation from proto comments

Usage Example

skill:
  name: protobuf-grpc-designer
  context:
    protoDirectory: ./proto
    targetLanguages:
      - go
      - python
      - typescript
    enableBufLint: true
    checkBreakingChanges: true
    streamingRequired: true

Best Practices

  1. Use package names that reflect domain boundaries
  2. Reserve field numbers when removing fields
  3. Use well-known types (Timestamp, Duration, etc.)
  4. Document all messages and fields with comments
  5. Version services through package names
  6. Implement proper error handling with Status codes

What ships with it: 1 file

684 B alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.