CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/grpc-golang/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-organized and efficiently written with a clear sequenced workflow and a verification step. Its main weakness is that the detailed implementation guidance is offloaded to a playbook file that is not present in the bundle, which hurts both actionability and progressive disclosure.

Suggestions

Add the missing resources/implementation-playbook.md (or remove the reference) so the deferred mTLS, interceptor, and streaming code patterns are actually available.

Inline at least one minimal executable Go snippet for mTLS or an interceptor so the skill is actionable without relying solely on the external playbook.

Tighten the Overview so it does not restate the frontmatter description, trimming the minor over-explanation.

DimensionReasoningScore

Conciseness

The body is well-sectioned with lean bullets and a short proto example and does not explain basic concepts Claude already knows, but the Overview and a few bullets restate context from the description, fitting the 4 anchor with minor trim opportunities.

4 / 5

Actionability

It provides one executable proto example and concrete commands ("buf lint", "buf generate"), but the bulk of implementation guidance (mTLS setup, interceptors) is deferred to resources/implementation-playbook.md, which does not exist, leaving the in-body guidance incomplete with missing key details — matching the 3 anchor.

3 / 5

Workflow Clarity

The six-step guide is clearly sequenced and includes a verification checkpoint ("Always run buf lint and breaking change checks before finalizing"), matching the 4 anchor, though only a single validation step is present.

4 / 5

Progressive Disclosure

Section structure is good and the playbook reference is one level deep and clearly signaled, but the referenced resources/implementation-playbook.md does not exist (no resources/ bundle directory), so navigation is broken — a real organization gap that fits the 3 anchor rather than 4.

3 / 5

Total

14

/

20

Passed

Description

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

The description is strong: it concisely states concrete capabilities and pairs them with an explicit "Use when" trigger clause, giving it clear distinctiveness. Minor specificity gains are possible by enumerating discrete actions, but it already answers both what and when well.

DimensionReasoningScore

Specificity

"Build production-ready gRPC services in Go with mTLS, streaming, and observability" names the domain plus several concrete capabilities, but presents them as a capability summary rather than an enumerated list of discrete actions, matching the 4 anchor and falling short of the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers "what" (build production-ready gRPC services with mTLS, streaming, observability) and "when" ("Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport") with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "gRPC services in Go", "mTLS", "streaming", "Protobuf contracts", "Buf" — giving good keyword coverage, though a few synonyms or extensions (e.g., .proto) are missing, fitting the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

The gRPC-Go + mTLS + Protobuf/Buf niche is specific with distinct triggers and minimal overlap risk with other skills, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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