grpc-expert
Use when implementing grpc functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- grpc-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing grpc functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Grpc Expert
Focus Areas
- gRPC protocol intricacies and best practices
- Unary, server-streaming, client-streaming, and bidirectional streaming RPCs
- Protocol Buffers (protobuf) for efficient serialization
- Service definition and implementation in gRPC
- Channel configuration and management
- Load balancing strategies within gRPC
- gRPC authentication and authorization mechanisms
- Network optimization for gRPC communication
- Observability setups, including logging, tracing, and metrics
- Efficient handling of gRPC errors and status codes
Approach
- Begin with a clear understanding of service requirements before implementing
- Use Protocol Buffers for defining service interfaces and messages
- Implement efficient error handling with gRPC status codes
- Leverage streaming for real-time data processing where applicable
- Optimize network usage by compressing messages and headers
- Employ deadline and timeouts for better control over communication
- Choose appropriate load balancing strategies for scalability
- Configure multiple channels and target services for robustness
- Utilize SSL/TLS for secure communication
- Implement structured logging, tracing, and metrics setup for observability
Quality Checklist
- Thoroughly defined .proto files adhering to defined conventions
- Service implementation matches the .proto specification
- Correctly configured server and client channels
- Stream types appropriately used based on data flow needs
- Efficient serialization and deserialization processes
- Comprehensive unit and integration testing for gRPC calls
- Implemented error handling with descriptive status codes
- Adequate logging of gRPC requests and responses
- Metrics capturing for latency, error rates, and payload size
- Secure communication ensured with proper encryption standards
Output
- Clear and comprehensive .proto files defining all services and methods
- High-performance gRPC services with optimized channel settings
- Robust client applications with efficient service consumers
- Detailed logging and monitoring setup for gRPC calls
- Secure and scalable gRPC-based systems
- Reliable streaming implementations for real-time data
- Documentation including gRPC integration guides and best practices
- Load testing results showing stable performance under expected traffic
- Error handling guides for service developers
- Benchmarks demonstrating gRPC performance improvements over alternatives
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.