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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill grpc-service-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mainly of boilerplate metadata rather than actionable content. It fails to explain what the skill actually does, provides no natural trigger terms beyond the skill name, and lacks any 'Use when' guidance. Claude would struggle to appropriately select this skill from a list of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates gRPC service definitions, creates .proto files, scaffolds server and client stubs, and configures service endpoints.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions gRPC, protobuf, proto files, RPC services, service definitions, or needs to create API endpoints using gRPC.'
Add common variations of terminology users might use: 'proto', 'protobuf', 'protocol buffers', 'RPC', 'service stubs', '.proto files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Grpc Service Generator') and mentions 'Backend Development' but provides no concrete actions like 'generates service stubs', 'creates proto files', or 'scaffolds gRPC endpoints'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause or trigger guidance. Both what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('grpc service generator, grpc service generator'). Missing natural variations users would say like 'proto', 'protobuf', 'RPC', 'service definition', or 'gRPC API'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'gRPC' is a specific technology that provides some distinctiveness, the generic 'Backend Development' category and lack of specific actions could cause overlap with other backend or code generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic marketing-style descriptions without any concrete guidance on how to generate gRPC services. A useful skill would include proto file examples, code generation commands, service implementation patterns, and validation steps.
Suggestions
Add concrete proto file examples showing service definitions with request/response message types
Include executable code generation commands (e.g., `protoc --go_out=. --go-grpc_out=. service.proto`)
Provide a step-by-step workflow: 1) Define proto, 2) Generate code, 3) Implement handlers, 4) Validate with grpcurl or similar
Add language-specific implementation examples for Node.js, Python, and Go since these are listed as related tags
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific steps for generating gRPC services. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints for generating gRPC services. The 'Capabilities' section lists vague promises rather than actual procedures. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, schemas, or templates that would be essential for gRPC service generation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.