[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CQ55QSDNTGF6FCAFXEYA5":3,"skill-same:01M78CQ55QSDNTGF6FCAFXEYA5":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M78CQ55QSDNTGF6FCAFXEYA5","grpc-golang",null,"Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fgrpc-golang\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: grpc-golang\ndescription: \"Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.\"\nrisk: safe\nsource: self\ndate_added: \"2026-02-27\"\n---\n\n# gRPC Golang (gRPC-Go)\n\n## Overview\n\nComprehensive guide for designing and implementing production-grade gRPC services in Go. Covers contract standardization with Buf, transport layer security via mTLS, and deep observability with OpenTelemetry interceptors.\n\n## Use this skill when\n\n- Designing microservices communication with gRPC in Go.\n- Building high-performance internal APIs using Protobuf.\n- Implementing streaming workloads (unidirectional or bidirectional).\n- Standardizing API contracts using Protobuf and Buf.\n- Configuring mTLS for service-to-service authentication.\n\n## Do not use this skill when\n\n- Building pure REST\u002FHTTP public APIs without gRPC requirements.\n- Modifying legacy `.proto` files without the ability to introduce a new API version (e.g., `api.v2`) or ensure backward compatibility.\n- Managing service mesh traffic routing (e.g., Istio\u002FLinkerd), which is outside the application code scope.\n\n## Step-by-Step Guide\n\n1. **Confirm Technical Context**: Identify Go version, gRPC-Go version, and whether the project uses Buf or raw protoc.\n2. **Confirm Requirements**: Identify mTLS needs, load patterns (unary\u002Fstreaming), SLOs, and message size limits.\n3. **Plan Schema**: Define package versioning (e.g., `api.v1`), resource types, and error mapping.\n4. **Security Design**: Implement mTLS for service-to-service authentication.\n5. **Observability**: Configure interceptors for tracing, metrics, and structured logging.\n6. **Verification**: Always run `buf lint` and breaking change checks before finalizing code generation.\n\nRefer to `resources\u002Fimplementation-playbook.md` for detailed patterns, code examples, and anti-patterns.\n\n## Examples\n\n### Example 1: Defining a Service & Message (v1 API)\n\n```proto\nsyntax = \"proto3\";\npackage api.v1;\noption go_package = \"github.com\u002Forg\u002Frepo\u002Fgen\u002Fapi\u002Fv1;apiv1\";\n\nservice UserService {\n  rpc GetUser(GetUserRequest) returns (GetUserResponse);\n}\n\nmessage User {\n  string id = 1;\n  string name = 2;\n}\n\nmessage GetUserRequest {\n  string id = 1;\n}\n\nmessage GetUserResponse {\n  User user = 1;\n}\n```\n\n## Best Practices\n\n- ✅ **Do:** Use Buf to standardize your toolchain and linting with `buf.yaml` and `buf.gen.yaml`.\n- ✅ **Do:** Always use semantic versioning in package paths (e.g., `package api.v1`).\n- ✅ **Do:** Enforce mTLS for all internal service-to-service communication.\n- ✅ **Do:** Handle `ctx.Done()` in all streaming handlers to prevent resource leaks.\n- ✅ **Do:** Map domain errors to standard gRPC status codes (e.g., `codes.NotFound`).\n- ❌ **Don't:** Return raw internal error strings or stack traces to gRPC clients.\n- ❌ **Don't:** Create a new `grpc.ClientConn` per request; always reuse connections.\n\n## Troubleshooting\n\n- **Error: Inconsistent Gen**: If the generated code does not match the schema, run `buf generate` and verify the `go_package` option.\n- **Error: Context Deadline**: Check client timeouts and ensure the server is not blocking infinitely in streaming handlers.\n- **Error: mTLS Handshake**: Ensure the CA certificate is correctly added to the `x509.CertPool` on both client and server sides.\n\n## Limitations\n\n- Does not cover service mesh traffic routing (Istio\u002FLinkerd configuration).\n- Does not cover gRPC-Web or browser-based gRPC integration.\n- Assumes Go 1.21+ and gRPC-Go v1.60+; older versions may have different APIs (e.g., `grpc.Dial` vs `grpc.NewClient`).\n- Does not cover L7 gRPC-aware load balancer configuration (e.g., Envoy, NGINX).\n- Does not address Protobuf schema registry or large-scale schema governance beyond Buf lint.\n\n## Resources\n\n- `resources\u002Fimplementation-playbook.md` for detailed patterns, code examples, and anti-patterns.\n- [Google API Design Guide](https:\u002F\u002Fcloud.google.com\u002Fapis\u002Fdesign)\n- [Buf Docs](https:\u002F\u002Fbuf.build\u002Fdocs)\n- [gRPC-Go Docs](https:\u002F\u002Fgrpc.io\u002Fdocs\u002Flanguages\u002Fgo\u002F)\n- [OpenTelemetry Go Instrumentation](https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Finstrumentation\u002Fgo\u002F)\n\n## Related Skills\n\n- @golang-pro - General Go patterns and performance optimization outside the gRPC layer.\n- @go-concurrency-patterns - Advanced goroutine lifecycle management for streaming handlers.\n- @api-design-principles - Resource naming and versioning strategy before writing `.proto` files.\n- @docker-expert - Containerizing gRPC services and configuring TLS cert injection via Docker secrets.\n","# gRPC Golang (gRPC-Go)\n\n## Overview\n\nComprehensive guide for designing and implementing production-grade gRPC services in Go. Covers contract standardization with Buf, transport layer security via mTLS, and deep observability with OpenTelemetry interceptors.\n\n## Use this skill when\n\n- Designing microservices communication with gRPC in Go.\n- Building high-performance internal APIs using Protobuf.\n- Implementing streaming workloads (unidirectional or bidirectional).\n- Standardizing API contracts using Protobuf and Buf.\n- Configuring mTLS for service-to-service authentication.\n\n## Do not use this skill when\n\n- Building pure REST\u002FHTTP public APIs without gRPC requirements.\n- Modifying legacy `.proto` files without the ability to introduce a new API version (e.g., `api.v2`) or ensure backward compatibility.\n- Managing service mesh traffic routing (e.g., Istio\u002FLinkerd), which is outside the application code scope.\n\n## Step-by-Step Guide\n\n1. **Confirm Technical Context**: Identify Go version, gRPC-Go version, and whether the project uses Buf or raw protoc.\n2. **Confirm Requirements**: Identify mTLS needs, load patterns (unary\u002Fstreaming), SLOs, and message size limits.\n3. **Plan Schema**: Define package versioning (e.g., `api.v1`), resource types, and error mapping.\n4. **Security Design**: Implement mTLS for service-to-service authentication.\n5. **Observability**: Configure interceptors for tracing, metrics, and structured logging.\n6. **Verification**: Always run `buf lint` and breaking change checks before finalizing code generation.\n\nRefer to `resources\u002Fimplementation-playbook.md` for detailed patterns, code examples, and anti-patterns.\n\n## Examples\n\n### Example 1: Defining a Service & Message (v1 API)\n\n```proto\nsyntax = \"proto3\";\npackage api.v1;\noption go_package = \"github.com\u002Forg\u002Frepo\u002Fgen\u002Fapi\u002Fv1;apiv1\";\n\nservice UserService {\n  rpc GetUser(GetUserRequest) returns (GetUserResponse);\n}\n\nmessage User {\n  string id = 1;\n  string name = 2;\n}\n\nmessage GetUserRequest {\n  string id = 1;\n}\n\nmessage GetUserResponse {\n  User user = 1;\n}\n```\n\n## Best Practices\n\n- ✅ **Do:** Use Buf to standardize your toolchain and linting with `buf.yaml` and `buf.gen.yaml`.\n- ✅ **Do:** Always use semantic versioning in package paths (e.g., `package api.v1`).\n- ✅ **Do:** Enforce mTLS for all internal service-to-service communication.\n- ✅ **Do:** Handle `ctx.Done()` in all streaming handlers to prevent resource leaks.\n- ✅ **Do:** Map domain errors to standard gRPC status codes (e.g., `codes.NotFound`).\n- ❌ **Don't:** Return raw internal error strings or stack traces to gRPC clients.\n- ❌ **Don't:** Create a new `grpc.ClientConn` per request; always reuse connections.\n\n## Troubleshooting\n\n- **Error: Inconsistent Gen**: If the generated code does not match the schema, run `buf generate` and verify the `go_package` option.\n- **Error: Context Deadline**: Check client timeouts and ensure the server is not blocking infinitely in streaming handlers.\n- **Error: mTLS Handshake**: Ensure the CA certificate is correctly added to the `x509.CertPool` on both client and server sides.\n\n## Limitations\n\n- Does not cover service mesh traffic routing (Istio\u002FLinkerd configuration).\n- Does not cover gRPC-Web or browser-based gRPC integration.\n- Assumes Go 1.21+ and gRPC-Go v1.60+; older versions may have different APIs (e.g., `grpc.Dial` vs `grpc.NewClient`).\n- Does not cover L7 gRPC-aware load balancer configuration (e.g., Envoy, NGINX).\n- Does not address Protobuf schema registry or large-scale schema governance beyond Buf lint.\n\n## Resources\n\n- `resources\u002Fimplementation-playbook.md` for detailed patterns, code examples, and anti-patterns.\n- [Google API Design Guide](https:\u002F\u002Fcloud.google.com\u002Fapis\u002Fdesign)\n- [Buf Docs](https:\u002F\u002Fbuf.build\u002Fdocs)\n- [gRPC-Go Docs](https:\u002F\u002Fgrpc.io\u002Fdocs\u002Flanguages\u002Fgo\u002F)\n- [OpenTelemetry Go Instrumentation](https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Finstrumentation\u002Fgo\u002F)\n\n## Related Skills\n\n- @golang-pro - General Go patterns and performance optimization outside the gRPC layer.\n- @go-concurrency-patterns - Advanced goroutine lifecycle management for streaming handlers.\n- @api-design-principles - Resource naming and versioning strategy before writing `.proto` files.\n- @docker-expert - Containerizing gRPC services and configuring TLS cert injection via Docker secrets.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","self","2026-02-27","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fgrpc-golang","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill grpc-golang",{"tool":40,"command":41},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill grpc-golang",{"tool":43,"command":44},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill grpc-golang","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fgrpc-golang\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"resources\u002Fimplementation-playbook.md","REFERENCE","参考文档",15018,"https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fgrpc-golang\u002Fresources\u002Fimplementation-playbook.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]