CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/load-testing-overview

Teaches load and performance testing from zero: a tool-selection table choosing between k6, JMeter, Gatling, Locust, and Artillery from observable project facts; the six load profiles (smoke, average-load, stress, spike, soak, breakpoint); open vs closed workload models; why percentiles beat averages; turning a run into a pass/fail CI gate with a first runnable k6 script; a performance-incident triage workflow (confirm with a k6 smoke run, flame-graph the hot path, check slow queries, localize the cause); and full Gatling (Simulation DSL, injectOpen/injectClosed, setUp().assertions()) and Locust (HttpUser + @task locustfile, headless / distributed runs, CSV gating) deep dives in references. Use when a service needs performance coverage and the tool, load profile, or pass/fail threshold has not been decided yet, or when a live performance incident needs cause localization.

75

Quality

94%

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%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.

The body is dense, actionable, and well-structured with executable examples, a well-sequenced incident workflow with checkpoints, and clean progressive disclosure into verified reference files. The only real weakness is minor verbosity in the workload-model explanation.

Suggestions

Tighten the 'Open vs closed workload models' section by collapsing the three k6 quotes into a single concise paraphrase plus one citation to reduce token cost.

Consider moving the jq summary-parsing one-liner and the EXPLAIN jq snippet into references/tool-executors.md or a CI-gating reference to keep the overview lean.

DimensionReasoningScore

Conciseness

Signal density is high with little padding of concepts Claude already knows, but the open-vs-closed section re-quotes documentation at length and some practitioner-convention prose could be tightened.

4 / 5

Actionability

Provides copy-paste-ready executable k6 scripts, install commands, run commands, threshold examples, and jq one-liners covering the common cases from zero to a failing CI gate.

5 / 5

Workflow Clarity

The incident workflow is a clear four-step sequence with explicit validation checkpoints and stop conditions (confirm-and-reproduce, flame-graph, slow-query, localize), plus a re-run-after-fix feedback loop.

5 / 5

Progressive Disclosure

SKILL.md is an overview with clearly signaled one-level-deep references to real bundle files (gatling.md, locust.md, tool-executors.md, traps.md), with deep-dive content appropriately split out.

5 / 5

Total

19

/

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.

The description is specific, well-triggered, and clearly distinguishes itself from sibling skills via explicit 'Use when' guidance and cross-references. It is comprehensive and concise despite its length, though slightly technical in its trigger vocabulary.

DimensionReasoningScore

Specificity

Lists many concrete actions including the five-tool selection table, six named load profiles, open/closed workload models, percentile-based CI gating, a first runnable k6 script, an incident-triage workflow, and Gatling/Locust deep dives, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what the skill does and when to use it via a clear 'Use when a service needs performance coverage... or when a live performance incident needs cause localization' clause alongside the detailed capability list.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('load and performance testing', 'a service needs performance coverage', 'a live performance incident') and the six profile names, though coverage is slightly technical-heavy and could use a few more common synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (load/perf tool selection and incident triage) and explicitly defers to the dedicated k6-load-testing and jmeter-load-testing skills, minimizing overlap risk.

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