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
88
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 defines what the skill does (set up JMeter performance testing, create scripts, configure and run load tests) and when to use it (with explicit trigger phrases and a 'Use when' clause). The description is specific to JMeter in Java projects, making it highly distinctive and unlikely to conflict with other skills.
| 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 run-jmeter.sh script, configuring load tests, running performance tests) and 'when' (explicit 'Use when' clause at the start plus 'This should trigger for requests such as...' with concrete examples). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'JMeter performance testing', 'Add JMeter support', 'load tests', 'performance tests', and explicit example phrases like 'Improve the code with JMeter performance testing' and 'Refactor the code with JMeter performance testing'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to JMeter performance testing for Java projects, with specific mentions of run-jmeter.sh script, loops/threads/ramp-up configuration, and the cursor-rules-java project context. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured skill that clearly sequences the workflow and appropriately delegates detailed content to a reference file. Its main weaknesses are redundancy across sections (the 'What is covered,' constraints, and workflow overlap significantly) and the lack of any concrete executable code in the body itself, making it dependent on the reference file for all actionable content.
Suggestions
Remove the 'What is covered in this Skill?' section or merge its unique points into the constraints/workflow to reduce redundancy and improve conciseness.
Include at least a minimal executable example in the body, such as the jmeter --version check command and the chmod +x command in a code block, so the skill has some standalone actionability without requiring the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary repetition — the 'What is covered' section largely duplicates the constraints and workflow sections. The 'When to use this skill' section repeats the description verbatim. However, it's not excessively verbose and avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides a clear workflow and mentions specific commands (jmeter --version, chmod +x), but the actual script template is deferred entirely to a reference file. There's no executable code or concrete example in the skill body itself — Claude must read the reference to do anything meaningful. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced with a prerequisite verification step first, followed by reading the template, creating the script, and documenting usage. The constraint about stopping if JMeter isn't installed and asking clarifying questions for ambiguous requests provides adequate validation checkpoints. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with a single, well-signaled reference to the detailed template file (references/151-java-performance-jmeter.md). The structure appropriately keeps the overview concise while deferring the full script template to a reference — one level deep with clear navigation. | 3 / 3 |
Total | 10 / 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
762cb86
- 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.