CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-grpc

Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A well-structured, highly actionable gRPC best-practices reference with executable code and properly split one-level-deep references. Its main weakness is workflow clarity: it is topical rather than sequenced and lacks explicit validation feedback loops for the batch/destructive operations it discusses.

Suggestions

Add an explicit ordered workflow for the Build and Review modes (e.g. 1. define proto → 2. generate → 3. validate generated code compiles → 4. implement server with interceptors/health → 5. write bufconn tests) with a validation checkpoint after code generation.

Include a validate→fix→retry loop for graceful shutdown and for batch/streaming handlers, since these are the destructive/batch-adjacent operations the cap calls out.

Trim the 'Persona'/'Modes' framing and consolidate the duplicate cross-reference lists (the inline godig/gopls bullets and the bottom Cross-References section) to recover a few tokens.

DimensionReasoningScore

Conciseness

Dense, value-dense reference that assumes Claude's competence and embeds rationale inline ('Kubernetes probes need it ...'), with no padding about what gRPC is; the 'Persona'/'Modes' framing and the multi-bullet skill cross-reference list are minor tokens that could be trimmed.

4 / 5

Actionability

Copy-paste-ready executable Go throughout (server setup, interceptor, client with retry/load-balancing config, error mapping, streaming) plus a Quick Reference table naming exact packages and a Common Mistakes table with concrete fixes covering common cases.

5 / 5

Workflow Clarity

Content is organized by concern rather than as a sequenced workflow; the shutdown snippet does include a timeout-fallback checkpoint, but there is no unified validate→fix→retry loop for the batch/destructive-adjacent operations (e.g. batch client streaming, graceful shutdown) the skill covers.

3 / 5

Progressive Disclosure

Clear overview body with well-signaled, one-level-deep links to real bundle files (references/protoc-reference.md, references/testing.md) that hold the bulk detail, plus a separate Cross-References section — content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

92%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 precise, third-person description that pairs a clear capability statement with an explicit, scenario-rich 'Use when' trigger. It is comprehensive and distinctive; the only minor gap is the absence of file-extension synonyms like '.proto'.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, ... streaming RPCs' — giving comprehensive coverage rather than a single generic verb.

5 / 5

Completeness

Explicitly answers 'what' ('Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices') and 'when' with a concrete 'Use when ...' clause enumerating trigger scenarios.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ('gRPC servers/clients', 'proto files', 'interceptors', 'status codes', 'TLS/mTLS', 'bufconn', 'streaming RPCs'), but a few common variations/synonyms (e.g. '.proto' extension, 'protobuf') are not all spelled out, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Narrow niche (gRPC for Golang microservices) with distinctive, specific triggers (interceptors, mTLS, bufconn) making overlap with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
samber/cc-skills-golang
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.