CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/jmeter-load-testing

Authors Apache JMeter `.jmx` test plans (Thread Groups + HTTP samplers + assertions + listeners) in the JMeter GUI, runs them headlessly via `jmeter -n -t plan.jmx -l results.jtl`, generates an HTML dashboard with `-e -o`, and gates CI on JTL parsing. Use when the project has an existing JMeter investment, needs JVM-native load tooling, or works in domains with strong JMeter community support (banking, telecom, enterprise).

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

High

Do not use without reviewing

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.

The body is dense, executable, and well-sequenced, with concrete commands, a CI gate, and an anti-patterns table. It respects the token budget while remaining copy-paste ready.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — no padding explaining what a CLI, CI, or load test is; every section delivers actionable density.

3 / 3

Actionability

Fully executable commands with exact flags, copy-paste-ready GitHub Actions YAML, concrete `awk` JTL parsing, and specific parameterization syntax (`${__P(...)}`).

3 / 3

Workflow Clarity

Clear install→run→parse→CI-gate sequence with an explicit pass/fail checkpoint (`exit 1` on threshold breach) and an anti-patterns table that doubles as guardrails.

3 / 3

Progressive Disclosure

Single self-contained file with well-organized sections and one-level-deep external references (Apache docs, sibling skills); no bundle files exist to reference, so inline organization is appropriate.

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.

The description is concrete, trigger-rich, and explicitly covers both capabilities and use-conditions in a distinctive niche. It is a strong, copy-ready skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with specific JMeter primitives (Thread Groups, HTTP samplers, assertions, listeners) and exact CLI flags (`jmeter -n -t plan.jmx -l results.jtl`, `-e -o`, JTL parsing).

3 / 3

Completeness

Explicitly answers both what (authoring, headless running, dashboard, CI gating) and when ('Use when the project has an existing JMeter investment...').

3 / 3

Trigger Term Quality

Strong natural coverage — 'JMeter', 'load tooling', 'JVM-native', 'JMeter investment' — terms a user would actually say when reaching for this skill.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to JMeter on the JVM with named domains (banking, telecom, enterprise), making it unlikely to trigger for k6/Gatling/Locust-style skills.

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