generating-grpc-services

Generate 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".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and concise with strong progressive disclosure and a clear step sequence, but it lacks inline executable examples and explicit validation checkpoints within the workflow. Adding a copy-paste protoc/grpcurl snippet and a verify step after compilation would lift the two score-2 dimensions.

Suggestions

Add one inline executable example (e.g., a minimal `.proto` snippet and the exact `protoc`/`buf` command) so the Instructions are copy-paste ready rather than referencing out for basic steps.

Insert an explicit validation checkpoint after the compile step (e.g., 'Run `buf lint` and confirm stubs generated before implementing handlers') to close the workflow feedback loop.

Tighten the Error Handling table by moving exhaustive codes into references and keeping only the highest-frequency cases inline, improving conciseness margin.

Dimension	Reasoning	Score
Conciseness	The body is dense with specifics and never explains concepts Claude already knows (no 'what gRPC is' preamble); every section earns its tokens, matching the lean score-3 anchor.	3 / 3
Actionability	Guidance is concrete (named status codes, 'grpc.health.v1.Health', mTLS, interceptors) but offers no inline executable code or copy-paste-ready commands — actual protoc invocations and proto snippets are deferred to references, leaving key details missing.	2 / 3
Workflow Clarity	A clear nine-step sequence exists, but it involves code generation and batch-style work with no explicit validation checkpoints (e.g., verify stubs compiled, run buf lint), which caps workflow clarity at 2 per the destructive/batch guidance.	2 / 3
Progressive Disclosure	A well-organized overview with three clearly signaled one-level-deep references (implementation.md, errors.md, examples.md), all verified to exist, with content appropriately split — matching the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it names concrete actions, provides natural user-facing trigger phrases, and explicitly covers both capability and usage conditions. It reads as a model third-person description with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generate gRPC service definitions, stubs, and implementations from Protocol Buffers' — matching the score-3 anchor for listing several specific actions, not merely naming a domain.	3 / 3
Completeness	Explicitly answers both 'what' (definitions, stubs, implementations) and 'when' ('Use when creating high-performance gRPC services. Trigger with phrases like...'), with no implicit-only trigger.	3 / 3
Trigger Term Quality	Natural trigger phrases a user would actually say — 'generate gRPC service', 'create gRPC API', 'build gRPC server' — give good coverage rather than jargon or a single keyword.	3 / 3
Distinctiveness Conflict Risk	Targets a clear gRPC-specific niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/api-development/grpc-service-generator/skills/generating-grpc-services/SKILL.md
Commit: 8585d6d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.