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; Create a JMeter test plan for a Java service. Part of Plinth Toolkit

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise skill body that points cleanly to a single reference file and gives concrete commands, with a clearly sequenced workflow and prerequisite validation. The main weaknesses are moderate content duplication between body and reference, and the absence of a post-creation verification step in the body workflow.

Suggestions

Remove the duplicated trigger-phrase list in 'When to use this skill' (it already appears verbatim in the description) and consolidate the prerequisite check so it lives in either Constraints or Workflow step 1, not both, to tighten conciseness.

Add an explicit post-creation validation step to the body workflow (e.g., 'Verify the script runs: ./run-jmeter.sh -h' and 'Confirm content matches the template exactly') so the feedback loop is visible without opening the reference.

De-duplicate the reference file against the body so each holds unique content (body = overview + workflow + triggers; reference = full template, project structure, usage examples), reducing the navigation overlap that currently caps progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and never explains concepts Claude already knows, but the 'When to use this skill' section duplicates the trigger phrases already in the description, the prerequisite check appears in both 'Constraints' and 'Workflow', and 'What is covered in this Skill?' overlaps the workflow steps — minor trim opportunities keep it just below a 5.	4 / 5
Actionability	Concrete commands and specifics are present (`jmeter --version`, `chmod +x run-jmeter.sh`, file paths, the -l/-t/-r/-g/-h options, JMETER_LOOPS/THREADS/RAMP_UP env vars), but the core deliverable (the script template) is referenced rather than shown inline, leaving a minor gap versus copy-paste-ready 5.	4 / 5
Workflow Clarity	A clear 4-step sequence with an explicit prerequisite validation checkpoint (verify jmeter --version, stop with guidance if missing) and edge-case handling (ambiguous scope -> ask; missing inputs -> report), but the body workflow lacks a post-creation verification step (the verify/functional checks live only in the reference file).	4 / 5
Progressive Disclosure	Well-organized overview (What is covered, Scope, Constraints, When to use, Workflow, Reference) with a clearly signaled one-level-deep link to references/151-java-performance-jmeter.md, which exists in the bundle; held below 5 because the reference file duplicates substantial body content and the actual script template is a second hop away in scripts/run-jmeter.sh.	4 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

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 that clearly states what the skill does and when to use it, with excellent natural trigger phrases. The only ding is the second-person 'you need' voice, which costs one specificity point per the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('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'), which would be a 5, but the second-person phrasing 'Use when you need to set up' triggers the mandated 1-point specificity reduction.	4 / 5
Completeness	Explicitly answers both 'what' (set up JMeter testing, create the script from the exact template, configure load tests, run tests) and 'when' ('Use when you need to set up JMeter performance testing for a Java project' plus concrete trigger phrases).	5 / 5
Trigger Term Quality	Comprehensive coverage of natural trigger phrases users would actually say ('Improve the code with JMeter performance testing', 'Apply JMeter performance testing', 'Refactor the code with JMeter performance testing', 'Add JMeter support', 'Create a JMeter test plan for a Java service'), plus the file artifact name run-jmeter.sh.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (JMeter performance testing for a Java project) with distinct, specific triggers and the named artifact run-jmeter.sh, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/151-java-performance-jmeter/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.