CtrlK
BlogDocsLog inGet started
Tessl Logo

151-java-performance-jmeter

Use when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with loops, threads, and ramp-up, or running performance tests from the project root with custom or default settings. This should trigger for requests such as Improve the code with JMeter performance testing; Apply JMeter performance testing; Refactor the code with JMeter performance testing; Add JMeter support. Part of cursor-rules-java project

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 well-crafted, concise skill body: it gives concrete commands and paths, a clearly sequenced workflow with a prerequisite validation gate, and clean one-level-deep navigation to the bundled reference and script template. No significant weaknesses found.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and contains no concept explanations Claude already knows; every section earns its place despite mild structural overlap between 'What is covered' and 'Workflow'.

3 / 3

Actionability

Provides concrete executable commands ('chmod +x run-jmeter.sh', 'jmeter --version'), specific option flags (-l, -t, -r, -g, -h), env vars (JMETER_LOOPS/THREADS/RAMP_UP), and exact file paths, correctly delegating the large verbatim template to a bundled reference rather than inlining it.

3 / 3

Workflow Clarity

A clear 4-step numbered sequence with an explicit prerequisite validation checkpoint ('Check jmeter --version and stop with guidance if not installed') and a Constraints checklist; the operation is non-destructive so the absence of a post-creation feedback loop does not cap the score.

3 / 3

Progressive Disclosure

A clear overview with a well-signaled one-level-deep reference link ([references/151-java-performance-jmeter.md]) that in turn points to the script asset (scripts/run-jmeter.sh); content is appropriately split between overview, detailed reference, and template asset with easy navigation.

3 / 3

Total

12

/

12

Passed

Description

90%

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 with explicit what/when triggers and good natural trigger-term coverage. Its only real weakness is the second-person voice in the opening clause, which triggers the rubric's specificity penalty.

Suggestions

Rephrase the opening in third person (e.g., 'Sets up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template...') to avoid the second-person voice penalty on specificity.

Drop the trailing 'Part of cursor-rules-java project' from the description; it is project metadata that adds no trigger value and dilutes the trigger signal.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('creating the run-jmeter.sh script from the exact template', 'configuring load tests with loops, threads, and ramp-up', 'running performance tests from the project root'), which would be a 3, but the opening 'Use when you need to set up' is second-person voice and the rubric guideline mandates a 1-point specificity penalty for that.

2 / 3

Completeness

Clearly answers both what (set up JMeter testing, create the script, configure load tests, run tests) and when via an explicit 'Use when...' clause plus 'This should trigger for requests such as...', so completeness is not capped at 2.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases users would say are enumerated: 'Improve the code with JMeter performance testing; Apply JMeter performance testing; Refactor the code with JMeter performance testing; Add JMeter support', giving good coverage of likely requests.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to JMeter performance testing for a Java project with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.

Repository
jabrena/cursor-rules-java
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.