CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/load-testing-overview

Teaches load and performance testing from zero: how to choose between k6, JMeter, Gatling, Locust, and Artillery based on observable project facts (team language, tests-as-code vs GUI authoring, protocols beyond HTTP, CI gating needs); the six load profiles (smoke, average-load, stress, spike, soak, breakpoint) and the question each one answers; the difference between open workload models that hold arrival rate constant and closed models that hold concurrent users constant; why percentiles rather than averages are the unit of measurement; and how to turn a run into a pass/fail CI gate, with a first runnable k6 script. Use when a service needs performance coverage and the tool, the load profile, or the pass/fail threshold has not been decided yet.

76

Quality

95%

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

92%

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

An actionable, well-structured overview skill: an executable k6 script, a concrete tool-picking table, an explicit smoke-first workflow with CI-gate validation, and two genuine one-level-deep reference files. The main drag is conciseness — extensive verbatim doc-quoting could be paraphrased to trim tokens.

Suggestions

Paraphrase the long verbatim quotes in the tool table's 'Why' column and the open/closed section into short practitioner summaries, linking out for the original docs.

Trim the opening definition ('Load testing drives concurrent, sustained traffic...') since Claude already knows what load testing is; keep only the laptop-dev-server caveat.

DimensionReasoningScore

Conciseness

Mostly high-signal practitioner content (open vs closed, 'coordinated omission', the six profiles), but heavy direct quoting from tool docs — the long 'Why' cells in the tool table and multi-sentence k6 quotes — adds tokens that paraphrasing would tighten, so it lands below 'lean and efficient'.

2.5 / 3

Actionability

A fully runnable k6 script with options, thresholds, and a default function, plus concrete install and run commands and a copy-paste-ready 'observable fact → pick' table — executable and complete.

3 / 3

Workflow Clarity

Clear sequence with explicit checkpoints: 'Run smoke first, always', then 'Only after it is green should you raise VUs or switch to an arrival-rate executor', validated by the green-check threshold and non-zero-exit CI gate.

3 / 3

Progressive Disclosure

Overview lives in SKILL.md while detail is split into two real, one-level-deep, clearly signaled references — [references/tool-executors.md] and [references/traps.md] — both present in the bundle and described before linking.

3 / 3

Total

11.5

/

12

Passed

Description

95%

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, highly specific description with an explicit 'Use when' trigger and a clear distinction from the per-tool skills. Its sole weakness is verbosity — a single long padded sentence — which the 'do not reward verbosity' guideline pulls just below the maximum.

Suggestions

Split into two shorter sentences: lead with the core capability, then the 'Use when' trigger, and trim the parenthetical enumerations (CI gating needs, the six profile names) that the body already covers in full.

DimensionReasoningScore

Specificity

Lists concrete actions — 'choose between k6, JMeter, Gatling, Locust, and Artillery', 'the six load profiles', 'turn a run into a pass/fail CI gate' — but the description is one padded sentence bristling with parenthetical enumerations, so the rubric's 'do not reward verbosity' guideline holds it below the max.

2.5 / 3

Completeness

Both halves are explicit: a clear 'what' enumeration and an explicit trigger, 'Use when a service needs performance coverage and the tool, the load profile, or the pass/fail threshold has not been decided yet.'

3 / 3

Trigger Term Quality

Natural user-facing terms are present and well covered — 'load and performance testing', 'load profile', 'pass/fail threshold' — alongside tool names (k6, JMeter, Gatling, Locust, Artillery) a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche as the overview/decision skill ('from zero'), and its trigger fires only when the tool, profile, or threshold 'has not been decided yet', distinguishing it from the per-tool deep-dive skills listed at the end.

3 / 3

Total

11.5

/

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