CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/grpcurl-cli

Wraps grpcurl, the curl-equivalent CLI for gRPC. Covers descriptor sources (server reflection default, --import-path + --proto for proto files, --protoset for compiled descriptor sets), service discovery (`list`, `describe`), invoking unary RPCs (`-d '{...}'`, `-d @file.json`, `-d @` for stdin), streaming RPCs (newline-delimited JSON via stdin), TLS configuration (--cacert, --cert, --key, --insecure, --plaintext), header injection (-H 'Authorization: Bearer ...'), and exit codes. Use for ad-hoc gRPC debugging, smoke testing, scriptable PR-time gates, and CLI-based interaction with reflective gRPC services.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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 body of executable grpcurl guidance with clear workflows and verification steps. The only notable weakness is mild verbosity from repeated README-link boilerplate and a speculative bug-reproduction section that restates earlier material.

Suggestions

Collapse the four identical 'Per [grpcurl README](...)' preambles into a single references note to remove repetition.

Trim or fold the 'Reproducing a production bug' section, since it largely reuses the invoke + auth-header examples already shown.

Add an explicit validation/feedback step to the reflection-based smoke matrix (e.g., fail the job on unexpected codes rather than only emitting a WARN).

DimensionReasoningScore

Conciseness

The body is mostly lean and executable with no concept-padding, but the identical 'Per [grpcurl README](...)' preamble is repeated four times and the speculative 'Reproducing a production bug' section restates invoke/header patterns already shown — tightening these would reach a 3.

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands and a complete CI workflow YAML covering install, discovery, invocation, TLS, auth headers, streaming, and scripting — matching the 'fully executable; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sections are clearly sequenced (Install → Choose descriptor source → Running → Parsing → CI) with explicit verification checkpoints (exit code 0 → OK, non-zero → alert; scripting example extracts the error code) for the primary risky workflows.

3 / 3

Progressive Disclosure

With no bundle files present, the self-contained body is well-organized into clear sections and the References section points one level deep to the external README and sibling skills, satisfying the simple-skill allowance for a 3.

3 / 3

Total

11

/

12

Passed

Description

100%

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 covers a comprehensive set of concrete grpcurl capabilities and pairs them with explicit use-when triggers in third-person voice. It is clear, distinct, and unlikely to be triggered by the wrong skill.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions: descriptor sources, service discovery (`list`, `describe`), unary and streaming invocation, TLS configuration, header injection, and exit codes — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers what ('Wraps grpcurl... Covers...') and when ('Use for ad-hoc gRPC debugging, smoke testing, scriptable PR-time gates...'), satisfying the explicit-trigger requirement for a 3.

3 / 3

Trigger Term Quality

It surfaces natural user-facing terms such as 'gRPC debugging', 'smoke testing', 'grpcurl', and 'RPC' alongside the more technical phrasing, giving good coverage of what a user would say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific (the grpcurl CLI for gRPC), with distinct triggers unlikely to collide with general-purpose skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents