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 with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be nearly useless for skill selection among multiple backend development skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates gRPC service definitions, proto files, server/client stubs, and service configurations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a gRPC service, generate .proto files, build RPC endpoints, or scaffold protobuf-based APIs.'
Include common keyword variations users might say: 'protobuf', 'proto file', '.proto', 'RPC service', 'gRPC API', 'service stub', 'protocol buffers'.
| 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 there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just a repeated label, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'grpc service generator' repeated twice. It misses natural user phrases like 'protobuf', 'proto file', 'gRPC endpoint', 'service definition', 'RPC', or '.proto'. Users rarely say 'grpc service generator' verbatim. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'grpc' provides some domain specificity that distinguishes it from generic backend skills, but the lack of concrete actions or scope means it could still overlap with other backend code generation or API-related 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 substantive content. It contains zero actionable information about gRPC service generation—no proto file examples, no code generation commands, no language-specific guidance, and no workflow. It reads as auto-generated boilerplate that would provide no value to Claude beyond what it already knows.
Suggestions
Add concrete, executable examples: include a sample .proto file definition, the protoc command to generate stubs, and a minimal server/client implementation in at least one language (e.g., Go or Python).
Define a clear multi-step workflow: e.g., 1) Define .proto file, 2) Generate code with protoc, 3) Implement service handlers, 4) Validate with grpcurl or a test client—with explicit validation checkpoints.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than providing actual technical guidance.
Add language-specific references or sub-files (e.g., GRPC_GO.md, GRPC_PYTHON.md) with copy-paste-ready templates for each supported language mentioned in the tags.
| 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 what the skill could do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The phrase 'step-by-step guidance' is mentioned but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no meaningful structure, no references to detailed files, and no actionable sections. The headings exist but contain only generic placeholder text. | 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
3076d78
- 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.