151-java-performance-jmeter
Provide a complete JMeter performance testing solution by creating the run-jmeter.sh script from the exact template, making it executable, and configuring the project structure for load testing.
Connecting the steps of a workflow
What it does
Provide a complete JMeter performance testing solution by creating the run-jmeter.sh script from the exact template, making it executable, and configuring the project structure for load testing. Supports custom loops, threads, ramp-up, and environment variable overrides.
Use when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
Includes 1 script
Your AI can run these when the skill is used — on your computer in a coding tool (which asks first unless you have told it not to), or in the AI’s own sandbox in Claude and ChatGPT.
How we know
Found in the skill’s folder: scripts/run-jmeter.sh.
1 smaller thing worth knowing
Contains commands that delete or overwrite. Usually legitimate — listed so nothing is hidden.
How we know
Contains commands that delete or overwrite — scripts/run-jmeter.sh line 157. Read 2026-10-05, commit 02e9d12.
scripts/run-jmeter.sh, line 157 ↗No serious risk pattern found
Launch7’s automated check read all 3 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 02e9d12 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to jabrena/plinth: 2026-10-04 (1 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Partly. Upload it in Claude’s settings — the instructions work; the scripts need the full folder.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
This skill ships 1 script beside its instructions. The download here is the SKILL.md alone — enough for the instructions, not for the parts that run code. Use the command route, or take the full folder from the repository.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from jabrena
All from this publisher →- 003-skills-inventory
Create a Checklist with all Java steps to use with system prompts for Java
- 012-agile-epic
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories.
- 013-agile-feature
Guides the creation of detailed agile feature documentation from an existing epic.
- 021-problem-framing
Guide production of a Problem statement, Current state, Desired state, Stakeholders, and Success criteria for a problem or issue under exploration.
- 022-root-cause-analysis
Guide the identification of root causes, not symptoms, for a framed problem, using Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification.
