generating-grpc-services
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-grpc-servicesGenerate gRPC service definitions, stubs, and implementations from Protocol Buffers. Use when creating high-performance gRPC services. Trigger with phrases like "generate gRPC service", "create gRPC API", or "build gRPC server".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill fails to provide gRPC-specific guidance despite its stated purpose. It reads like a generic REST API template with 'gRPC' substituted in the title. There are no proto file examples, no protoc commands, no actual gRPC service implementation patterns, and the output directories reference REST concepts (routes, controllers) rather than gRPC concepts (services, stubs, proto files).
Suggestions
Add concrete proto file examples showing service and message definitions (e.g., `service Greeter { rpc SayHello (HelloRequest) returns (HelloReply); }`)
Include executable protoc commands for generating stubs: `protoc --go_out=. --go-grpc_out=. service.proto`
Replace generic REST output paths with gRPC-specific outputs: proto files, generated stubs, server implementations
Add validation steps for proto compilation and service testing (e.g., using grpcurl or grpc_cli)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains significant padding and generic boilerplate that doesn't add value. Phrases like 'This skill provides automated assistance for grpc service generator tasks' are redundant. The prerequisites section lists generic development requirements Claude already knows. | 1 / 3 |
Actionability | No executable code, no concrete gRPC/protobuf examples, no actual proto file syntax or grpc-tools commands. Instructions are vague ('Generate boilerplate code using Bash(api:grpc-*)') without showing what that actually looks like or what commands to run. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbering (two separate '1-5' sequences). No validation checkpoints for proto compilation or service generation. Missing critical gRPC-specific workflow steps like protoc compilation, stub generation, and service registration. | 1 / 3 |
Progressive Disclosure | References external files (implementation.md, errors.md, examples.md) which is appropriate structure, but the main content is too thin to serve as a useful overview. The output paths listed are generic REST API paths, not gRPC-specific outputs. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
90%This is a well-structured skill description with clear trigger phrases and explicit 'Use when' guidance. The main weakness is that the capability list could be more comprehensive - it mentions definitions, stubs, and implementations but doesn't detail specific features like streaming support, authentication patterns, or language-specific generation.
Suggestions
Expand the capability list to include more specific actions like 'generate streaming endpoints', 'create client stubs', or 'implement interceptors' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (gRPC/Protocol Buffers) and lists some actions (generate definitions, stubs, implementations), but lacks comprehensive detail about specific capabilities like streaming, interceptors, or client generation. | 2 / 3 |
Completeness | Clearly answers both what (generate gRPC service definitions, stubs, and implementations from Protocol Buffers) and when (creating high-performance gRPC services) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'generate gRPC service', 'create gRPC API', 'build gRPC server', plus mentions Protocol Buffers. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting gRPC and Protocol Buffers specifically. Unlikely to conflict with general API skills or other service generation tools due to explicit gRPC terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.