CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/ghz-load

Wraps ghz, the gRPC load testing tool, for throughput and latency benchmarking. Covers test invocation (--proto + --call + host:port; or --protoset for compiled descriptors), load parameters (-n total requests, -c concurrency, -r RPS rate limit, -z duration), output formats (json/csv/html/influx-summary for CI consumption), the metrics reported (RPS achieved, latency p50/p95/p99, status-code distribution, errors), and CI integration patterns for regression gating. Use when benchmarking a gRPC service's throughput or detecting latency regressions in CI.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, action-oriented skill body with executable commands, a committed config, and a complete CI regression-gating workflow including a baseline-compare validation step. Organization is clear and external references are one level deep and well signaled.

DimensionReasoningScore

Conciseness

The body is lean and table/example-driven — flag tables, config JSON, and copy-paste commands — without explaining concepts Claude already knows (e.g. what gRPC or protobuf is), so every token largely earns its place.

3 / 3

Actionability

Provides fully executable commands ('ghz --proto=... --call=... -n 10000 -c 50'), a complete committed config.json, a complete compare-ghz.py script, and a GitHub Actions workflow — all copy-paste ready.

3 / 3

Workflow Clarity

Sequenced Install → Configure → Running → Parsing → CI sections, and the regression-gate workflow has an explicit baseline-compare validation checkpoint with a failure/exit-1 feedback path gating the gate.

3 / 3

Progressive Disclosure

No bundle files exist; references to sibling skills and ghz.sh docs are one level deep and clearly signaled in a References section, and the content is well-organized into navigable sections.

3 / 3

Total

12

/

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 concretely lists the tool's capabilities and provides an explicit third-person trigger clause for when to use it. It is gRPC-specific, distinguishing it from generic load-testing skills.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capabilities — 'test invocation (--proto + --call + host:port)', 'load parameters (-n... -c... -r... -z...)', 'output formats (json/csv/html/influx-summary)', 'metrics reported (RPS... latency p50/p95/p99, status-code distribution, errors)' and 'CI integration patterns' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (wraps ghz for throughput/latency benchmarking covering invocation, load, output, metrics, CI) and when via an explicit 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

The 'Use when benchmarking a gRPC service's throughput or detecting latency regressions in CI' clause supplies natural user phrasings (gRPC, throughput, latency regressions, benchmarking) with good coverage.

3 / 3

Distinctiveness Conflict Risk

Narrow gRPC-specific niche with distinct triggers (ghz, gRPC, latency regressions in CI) makes conflict with other skills unlikely.

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