grpc-golang

Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/grpc-golang/SKILL.md

Quality

Content

43%Scale 1-5

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

This skill provides a well-structured overview of gRPC in Go but falls short on actionability—it promises mTLS, streaming, and observability but only delivers a basic proto definition. The step-by-step guide reads as a generic checklist rather than executable workflow, and the referenced implementation playbook is missing from the bundle, leaving the skill hollow. The best practices and troubleshooting sections add genuine value but can't compensate for the missing core implementation guidance.

Suggestions

Add executable Go code examples for the key promised features: mTLS setup (tls.Config + grpc.Creds), a streaming handler with ctx.Done() handling, and an OpenTelemetry interceptor configuration.

Replace the abstract step-by-step guide with concrete commands (e.g., `buf lint`, `buf generate`, `buf breaking --against`) and include validation/feedback loops showing what to do when checks fail.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the critical patterns directly in the SKILL.md.

Remove the 'Use this skill when' / 'Do not use this skill when' sections or compress them significantly—these consume tokens on context Claude can infer from the skill's title and content.

Dimension	Reasoning	Score
Conciseness	The skill includes several sections that explain things Claude already knows (e.g., 'Use this skill when' / 'Do not use this skill when' lists are somewhat verbose, the Overview restates the description). The best practices and troubleshooting sections are reasonably tight, but the step-by-step guide is high-level padding without adding much actionable value. The 'Confirm Technical Context' and 'Confirm Requirements' steps are generic process steps Claude doesn't need spelled out.	3 / 5
Actionability	The proto example is concrete and useful, but the step-by-step guide is entirely abstract ('Confirm Requirements', 'Plan Schema', 'Security Design') with no executable code for the Go implementation side—no mTLS setup code, no interceptor code, no streaming handler code. The skill promises mTLS, streaming, and observability but only shows a basic proto definition. The real implementation is deferred to a referenced playbook that doesn't exist in the bundle.	3 / 5
Workflow Clarity	The 6-step guide is a rough sequence of high-level activities rather than a clear workflow with concrete commands and validation checkpoints. Step 6 mentions 'buf lint' but doesn't show the command or what to do if it fails. There are no feedback loops for error recovery. For a skill involving code generation and security configuration, the lack of validation steps is a significant gap.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns and code examples, which is a good structural decision. However, no bundle files are provided, so the referenced playbook doesn't exist, making the reference a dead link. The SKILL.md itself is structured with clear sections, but critical content (mTLS code, streaming examples, interceptor setup) is entirely absent from both the skill and the bundle.	3 / 5
	Total	11 / 20 Passed

Description

87%Scale 1-5

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 is a strong skill description that clearly defines a specific technical niche (gRPC services in Go) with concrete capabilities and explicit trigger conditions. The description is concise, uses proper third-person voice, and includes domain-specific terms that would naturally appear in user requests. Minor improvements could include additional synonym coverage for trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several specific actions and concepts: 'Build production-ready gRPC services', 'mTLS', 'streaming', 'observability', 'designing Protobuf contracts with Buf', 'secure service-to-service transport'. These are concrete but could be more comprehensive (e.g., mentioning interceptors, health checks, load balancing).	4 / 5
Completeness	Clearly answers both 'what' (build production-ready gRPC services in Go with mTLS, streaming, and observability) and 'when' (Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport). The 'Use when' clause provides explicit trigger scenarios.	5 / 5
Trigger Term Quality	Includes strong natural keywords like 'gRPC', 'Go', 'mTLS', 'streaming', 'Protobuf', 'Buf', 'service-to-service'. Missing some common variations users might say such as 'proto files', '.proto', 'protocol buffers', 'bidirectional streaming', or 'TLS certificates'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: gRPC + Go + mTLS + Buf is a very specific combination unlikely to overlap with other skills. The mention of Protobuf contracts and service-to-service transport further narrows the scope.	5 / 5
	Total	18 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/grpc-golang/SKILL.md
Commit: 0159794

Reviewed: 3 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.