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. Part of the skills-for-java project
74
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/151-java-performance-jmeter/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly communicates what the skill does (set up JMeter performance testing, create scripts, configure and run load tests) and when to use it (when working with JMeter in Java projects). The description includes specific technical terms that serve as natural trigger keywords and is distinctive enough to avoid conflicts with other skills. Minor note: it uses second person 'you' in the trigger clause, but the actions themselves are described in imperative/noun form rather than first/second person voice for the capability descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating the run-jmeter.sh script from a template, configuring load tests with loops/threads/ramp-up, and running performance tests with custom or default settings. | 3 / 3 |
Completeness | Clearly answers both what (creating JMeter scripts, configuring load tests, running performance tests) and when ('Use when you need to set up JMeter performance testing for a Java project') with explicit trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'JMeter', 'performance testing', 'Java project', 'load tests', 'threads', 'ramp-up', 'run-jmeter.sh'. These cover the domain well and match how users would describe their needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets JMeter performance testing specifically for Java projects, with specific mentions of the run-jmeter.sh script and load test configuration parameters. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is structured as a thin overview that delegates nearly all actionable content to a reference file, leaving the SKILL.md itself without executable examples or a clear step-by-step workflow. While it correctly identifies constraints and prerequisites, the lack of any concrete code or commands in the main file significantly reduces its standalone usefulness. The content also has moderate redundancy across its sections.
Suggestions
Include the actual step-by-step workflow (numbered steps) directly in the SKILL.md: verify JMeter, read template from reference, create file, chmod, validate, run — with explicit validation checkpoints.
Add at least a minimal executable example showing how to run the script (e.g., `./run-jmeter.sh -l 10 -t 5 -r 2`) and expected output or success criteria.
Remove the redundant 'What is covered' bullet list since it duplicates the opening paragraph and constraints section.
Consolidate the 'When to use this skill' triggers into a single concise sentence rather than four near-identical bullet points.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy — the 'What is covered' section largely repeats the opening paragraph and the constraints section. The 'When to use this skill' section lists four near-identical trigger phrases that add little value. However, it's not excessively verbose. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands beyond `chmod +x` and `jmeter --version`, and no actual script template. All real content is deferred to a reference file, leaving the skill itself as vague direction rather than concrete guidance. | 1 / 3 |
Workflow Clarity | There is an implicit sequence (verify JMeter → read reference → copy template → chmod → run), and the PREREQUISITE/CRITICAL/PERMISSION labels hint at ordering, but there are no explicit numbered steps, no validation checkpoints after script creation, and no error recovery guidance. | 2 / 3 |
Progressive Disclosure | The skill does reference a single external file for the detailed template and usage instructions, which is appropriate one-level-deep disclosure. However, the SKILL.md itself contains almost no actionable quick-start content — it's essentially just a pointer to the reference file with some metadata, making the split feel like it went too far. | 2 / 3 |
Total | 7 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
9ec21dd
- 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.