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.

71

Quality

89%

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

82%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 lean, highly actionable CLI skill body with executable commands and validation-aware batch workflows. Slight room to tighten the inline CI YAML and add an explicit fix-and-retry loop for the reproduce-a-bug path.

Suggestions

Move the full GitHub Actions workflow YAML into a references/ file and keep a minimal inline stub to reduce token weight.

Add an explicit validate -> fix -> retry feedback loop to the 'Reproducing a production bug' and CI smoke-test sections.

Consider splitting the flag reference table and reflection smoke matrix into a references/ doc to improve progressive disclosure now that the body exceeds ~250 lines.

DimensionReasoningScore

Conciseness

Dense with executable commands and tables and minimal prose padding; the embedded GitHub Actions YAML and reflection smoke matrix are useful but could be trimmed or moved to a reference, leaving minor verbosity.

4 / 5

Actionability

Copy-paste-ready commands for install, discovery, unary/streaming invocation, auth headers, and a full CI workflow cover the common cases end-to-end.

5 / 5

Workflow Clarity

Sequences are clear and batch operations (CI smoke test, reflection matrix) include validation via exit codes and grep checks; falls just short of 5 because the reproduce-a-bug and CI sections lack an explicit validate-then-fix feedback loop.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references to sibling-skill catalogs (status-codes.md, versioning-strategy.md); no bundle files exist, and some inline reference material (full CI YAML) could live in a separate file.

4 / 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 high-quality description: third-person voice, concrete capability list, and an explicit 'Use for' trigger clause. Only minor gap is missing a few natural keyword variants (.proto extension, 'reflection').

DimensionReasoningScore

Specificity

Lists multiple concrete actions across descriptor sources (server reflection, --import-path/--proto, --protoset), service discovery, unary and streaming RPC invocation, TLS config, header injection, and exit codes — comprehensive coverage matching the 5 anchor.

5 / 5

Completeness

Clearly states what the skill does ('Wraps grpcurl... Covers...') and gives an explicit 'Use for...' clause naming concrete triggers, matching the anchor that requires both what and when.

5 / 5

Trigger Term Quality

Includes natural terms like 'gRPC debugging', 'smoke testing', 'PR-time gates', and 'reflective gRPC services', but omits common variations such as the '.proto' file extension and 'reflection' as a standalone trigger keyword.

4 / 5

Distinctiveness Conflict Risk

Scoped narrowly to grpcurl/gRPC CLI interaction with distinct triggers; minimal overlap risk with sibling tools like ghz-load or grpc-mock, which it names separately.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents