CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/k6-load-testing

Authors k6 JavaScript load-test scripts (VU loops + checks + sleeps), configures the `options` block with `stages` (ramp-up patterns) and `thresholds` (p(95) latency, error rate), runs via `k6 run script.js` or `--vus / --duration` ad-hoc flags, and uses thresholds as the CI pass/fail signal. Includes a latency-percentile interpretation reference: tail ratio (p99/p50), bimodal-distribution detection, coordinated omission and why naive p99 is optimistic, and constant-vus vs constant-arrival-rate executors. Use when the project ships HTTP / WebSocket / gRPC load tests and the team wants developer-friendly JavaScript authoring, or when a k6 threshold passes but the system still feels slow.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

86%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 dense, executable, well-organized k6 reference that defers CI and latency-interpretation detail to real one-level-deep bundle files. Tightening repeated attribution lines and making threshold-failure recovery an explicit loop would push it to the top anchor.

Suggestions

Consolidate the repeated 'Per [k6-running][running]' attribution notes into a single citations section to reduce redundancy.

Add an explicit 'If a threshold fails' recovery loop in the Parsing results / CI section rather than relying on the static Anti-patterns table.

Drop parenthetical re-explanations under tables (e.g. 'the example above') where the table is already self-explanatory.

DimensionReasoningScore

Conciseness

Mostly lean with k6-specific facts that earn their place, but repeated 'Per [k6-running][running]' attribution lines and a few parenthetical table footnotes could be trimmed without losing clarity.

4 / 5

Actionability

Fully executable copy-paste-ready code throughout — minimal script, stages/thresholds/abortOnFail options, run commands, a flags table, a jq gate-report snippet — covering the common cases concretely.

5 / 5

Workflow Clarity

Logical install→author→run→parse→CI→interpret→anti-patterns sequence with threshold/exit-code/jq checkpoints, but recovery guidance lives in a static anti-patterns table rather than an explicit 'if threshold fails, do X' feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a well-structured overview with two clearly signaled one-level-deep references (ci-integration.md, latency-percentiles.md), both verified present, keeping detail appropriately split out of the main body.

5 / 5

Total

18

/

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 strong, specific, third-person description that clearly states capabilities and trigger conditions with concrete k6-flavored language. Minor keyword synonym coverage (performance testing, stress test) keeps trigger-term quality just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Authors k6 JavaScript load-test scripts', 'configures the options block with stages and thresholds', 'runs via k6 run script.js or --vus / --duration', 'uses thresholds as the CI pass/fail signal' — with comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (authors scripts, configures options, runs, interprets results) and when ('Use when the project ships HTTP / WebSocket / gRPC load tests... or when a k6 threshold passes but the system still feels slow') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('k6', 'load-test scripts', 'HTTP / WebSocket / gRPC load tests', 'p(95) latency', 'error rate', 'a k6 threshold passes but the system still feels slow'), though common synonyms like 'performance testing', 'stress test', and 'throughput' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear k6-specific niche with distinct triggers (k6, thresholds, VU loops) and is explicitly contrasted against JMeter/Gatling/Locust, minimizing conflict risk with sibling load-testing skills.

5 / 5

Total

19

/

20

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