CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/grpc-mock

Wraps gRPC server-mocking patterns for client-side tests: Go bufconn (in-memory net.Listener via google.golang.org/grpc/test/bufconn) + mockgen-generated interface mocks, Python pytest-grpc fixtures + unittest.mock patching of stubs, JVM grpc-mock library / in-process gRPC server (InProcessServerBuilder), Node @grpc/grpc-js fake server with NewServer-on-port-0. Also carries the interceptor-layer test patterns (Go / Java / grpc-js auth, retry, logging, error-mapping, chained ordering via a spy handler) in references/interceptors.md. Use when writing client-side tests that need a controllable gRPC server response (success cases, error cases, timeouts, single-response error injection) without spinning up a real backend, or when testing a gRPC interceptor. For multi-message streaming-sequence tests (server-streaming, bidi), use grpc-streaming-test-author instead. Distinct from grpcurl-cli (ad-hoc CLI invocation against a real server) and ghz-load (perf against a real server).

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

Passed

No findings from the security scan

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 strong, executable multi-language authoring guide with good structure and working code for Go, Python, JVM, and Node. Main weaknesses are mild repetition of an external status-code reference and the absence of explicit validation feedback loops.

Suggestions

Consolidate the repeated references/status-codes.md citations into a single mention to reduce redundancy and token cost.

Resolve the references/status-codes.md reference: either add the file to the bundle or reword it as a pointer to the grpc-streaming-test-author skill rather than a local path.

Add an explicit validate-fix-retry note in 'Parsing results' (e.g., fix error mapping → re-run → confirm status.Code()) to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is code-forward and mostly lean, but the status-code catalog reference ('references/status-codes.md') is repeated in the Overview, Go section, and Parsing results, which could be consolidated.

4 / 5

Actionability

Provides fully executable, copy-paste-ready examples for all four languages plus concrete install/run commands ('go install go.uber.org/mock/mockgen@latest', 'go test ./... -race -timeout=60s'), covering the common cases.

5 / 5

Workflow Clarity

Clear structure (When to use → Authoring by language → Running → Parsing results → Anti-patterns) with error-recovery guidance in 'Parsing results'; not a destructive/batch operation so no validation cap applies, but explicit validate-fix-retry loops are absent.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references with a dedicated References section, and the cited interceptor bundle files (interceptors.md, go-interceptors.md, java-interceptors.md, grpc-js-interceptors.md) all exist; minor gap is the repeated citation of references/status-codes.md which is not present in this bundle.

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 highly specific, well-scoped description that crisply states per-language mechanisms, gives an explicit 'Use when' trigger, and cleanly distinguishes the skill from its siblings. Only slight room to broaden natural-language trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete per-language actions — 'Go bufconn (in-memory net.Listener via google.golang.org/grpc/test/bufconn) + mockgen-generated interface mocks', 'Python pytest-grpc fixtures + unittest.mock patching', 'JVM ... InProcessServerBuilder', 'Node @grpc/grpc-js fake server with NewServer-on-port-0' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Wraps gRPC server-mocking patterns for client-side tests ...') and when ('Use when writing client-side tests that need a controllable gRPC server response ... or when testing a gRPC interceptor') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural domain terms ('gRPC server-mocking', 'client-side tests', 'interceptor', 'timeouts', 'error injection') that a user would say, but a few lay synonyms are absent and the phrasing leans technical.

4 / 5

Distinctiveness Conflict Risk

Clear niche (client-side gRPC server mocking) with explicit boundary statements — 'Distinct from grpcurl-cli ... and ghz-load' and 'use grpc-streaming-test-author instead' for streaming — minimizing conflict risk.

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: 4 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents