Name: grpc-golang
Rating: 60.8 (1 reviews)
Author: administrakt0r

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

71%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/grpc-golang/SKILL.md

The canonical home for this skill is grpc-golang in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%Weight 40%Scale 1-5

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

The body is concise and well-organized as an overview, but its core advertised capabilities lack executable code and the single referenced playbook file is a dangling pointer. Adding concrete Go examples for mTLS/streaming/interceptors and shipping the referenced resource would lift the actionability and progressive-disclosure scores.

Suggestions

Add executable Go code examples for the advertised mTLS, streaming, and OpenTelemetry-interceptor capabilities (currently only a proto example and abstract best-practice bullets are present).

Either create the referenced 'resources/implementation-playbook.md' with the detailed patterns/code/anti-patterns, or remove the dangling reference and inline a minimal version.

Strengthen the workflow with an explicit validate->fix->retry feedback loop around 'buf lint' and breaking-change checks (e.g., on failure, fix and re-run until clean before generating code).

Dimension	Reasoning	Score
Conciseness	Lean and well-sectioned with no over-explanation of concepts Claude already knows; assumes competence and earns its token budget (only minor redundancy in repeating the playbook reference).	5 / 5
Actionability	Provides one complete proto example and concrete buf commands, but the headline capabilities (mTLS, streaming, observability interceptors) have no executable Go code, leaving key implementation details missing.	3 / 5
Workflow Clarity	A clear 6-step sequence with a verification checkpoint exists, but for risky code-gen/breaking-change work the validation is a single mention with no validate->fix->retry feedback loop, which caps the score at 3.	3 / 5
Progressive Disclosure	The SKILL.md is structured as an overview pointing to a playbook, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle, leaving the navigation broken rather than clearly signaled.	3 / 5
	Total	14 / 20 Passed

Description

78%Weight 40%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.

A strong, specific description that clearly conveys both capabilities and triggering scenarios for a well-scoped gRPC-Go skill. Minor improvements would add trigger synonyms and file extensions like '.proto'.

Dimension	Reasoning	Score
Specificity	States multiple concrete capabilities ('mTLS, streaming, and observability') plus Protobuf/Buf contract design, fitting 'lists several specific actions; minor gaps' rather than the comprehensively enumerated actions of a 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Build production-ready gRPC services... with mTLS, streaming, and observability') and 'when' ('Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport'), but the 'when' could be more expansive with concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural terms like 'gRPC services in Go', 'mTLS', 'streaming', 'Protobuf contracts with Buf' give good keyword coverage, but common synonyms and file extensions (e.g. .proto) are missing, stopping short of a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (gRPC in Go with mTLS/streaming/Buf) with distinct transport-tech triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/grpc-golang/SKILL.md
Commit: 57c135b

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