grpc-service-generator
Grpc Service Generator - Auto-activating skill for Backend Development. Triggers on: grpc service generator, grpc service generator Part of the Backend Development skill category.
35
3%
Does it follow best practices?
Impact
95%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/grpc-service-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that restates the skill name without explaining what the skill does or when it should be selected. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates gRPC service definitions, proto files, server/client stubs, and boilerplate configuration for gRPC-based microservices.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a gRPC service, generate protobuf definitions, scaffold RPC endpoints, or set up a proto file.'
Include natural keyword variations users might say: 'protobuf', 'proto', '.proto file', 'RPC service', 'gRPC server', 'gRPC client', 'service stub'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Grpc Service Generator') and its category ('Backend Development') but lists no concrete actions like generating proto files, creating service stubs, or configuring gRPC endpoints. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is limited to a redundant trigger phrase with no explicit 'Use when...' guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'grpc service generator' repeated twice. There are no natural variations users might say such as 'protobuf', 'proto file', 'gRPC server', 'gRPC client', 'service definition', or 'RPC endpoint'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'grpc' does narrow the domain somewhat compared to a fully generic description, but the lack of specific actions or file types means it could overlap with other backend or code generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about gRPC service generation. It contains only generic boilerplate text that repeats the skill name without providing any actionable guidance, code examples, or workflow steps. It would provide zero value to Claude when attempting to generate gRPC services.
Suggestions
Add concrete, executable code examples showing proto file definitions, code generation commands (e.g., `protoc --go_out=...`), and sample server/client implementations in at least one language (Go, Python, or Node.js).
Define a clear multi-step workflow: 1) Define .proto file, 2) Generate stubs with specific commands, 3) Implement service handlers, 4) Validate with a test client—including validation checkpoints.
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) that just repeat the skill name, and replace with actual technical content about gRPC service patterns, common pitfalls, and best practices.
Add references to supplementary files for language-specific implementations (e.g., GO_GRPC.md, PYTHON_GRPC.md) if multi-language support is intended.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'grpc service generator' excessively, and provides zero actual technical content about generating gRPC services. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no proto file examples, no service definitions, no build steps. Every section is vague and abstract, describing rather than instructing. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no meaningful structure. There are no references to detailed files, no examples, and no navigation to deeper content. The sections that exist contain no useful information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.