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
77
71%
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 well-crafted skill description that clearly identifies its purpose, provides specific actions, and includes natural trigger terms. It follows the 'Use when...' pattern effectively and targets a distinct niche (JMeter + Java) that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating the run-jmeter.sh script from the exact template', 'configuring load tests with loops, threads, and ramp-up', and 'running performance tests from the project root with custom or default settings'. | 3 / 3 |
Completeness | Explicitly answers both what (setting up JMeter, creating scripts, configuring load tests, running tests) AND when ('Use when you need to set up JMeter performance testing for a Java project') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'JMeter', 'performance testing', 'Java project', 'load tests', 'loops', 'threads', 'ramp-up'. These are terms developers naturally use when discussing performance testing. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: JMeter performance testing for Java projects with specific script names and configuration parameters. Unlikely to conflict with other skills due to the specific tool (JMeter) and context (Java project, run-jmeter.sh). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured as an overview document with appropriate progressive disclosure, but critically lacks actionability - it repeatedly instructs to use an 'exact template' without including the template or any executable code. The content would be significantly improved by including at least the core script template or key commands inline.
Suggestions
Include the actual run-jmeter.sh template content inline or provide the essential code snippet that Claude needs to execute
Add explicit numbered workflow steps: 1) Check JMeter installation with specific command, 2) Create script, 3) Set permissions, 4) Verify script works
Provide the actual verification command and expected output for checking JMeter installation
Remove redundant statements about 'exact template' - state it once clearly in constraints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the 'What is covered' section largely repeats information from the description and constraints. The repeated emphasis on 'exact template' and 'do not modify' appears multiple times. | 2 / 3 |
Actionability | The skill describes what to do but provides no concrete code, commands, or the actual template content. It tells Claude to 'copy the template exactly' but the template itself is only in a referenced file, making this skill not actionable on its own. | 1 / 3 |
Workflow Clarity | There's an implicit sequence (verify JMeter → create script → make executable) but no explicit numbered steps or validation checkpoints. The prerequisite check is mentioned but not shown as part of a clear workflow with error handling. | 2 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview with a clear, single-level reference to the detailed guidance file. The structure is clean with distinct sections for scope, constraints, usage triggers, and reference. | 3 / 3 |
Total | 8 / 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.
7772a1b
Table of Contents
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.