jmeter-test-plan-creator

Name: jmeter-test-plan-creator
Author: jeremylongshore

github.com/jeremylongshoreTesting & quality2.9k104 installsUpdated 2d ago

About jmeter-test-plan-creator

A skill for JMeter performance-testing tasks, offering step-by-step plan guidance and generating configurations and code for developers working on load, stress, or benchmark tests.

Key features

01Guidance for JMeter test plans
02Generates code and configurations
03Applies performance-testing practices
04Checks outputs against common standards

Use cases

01Create a JMeter test plan
02Plan load or stress tests
03Get performance benchmarking guidance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill jmeter-test-plan-creator

After installing, type/jmeter-test-plan-creatorin Claude Code to confirm it loaded.

Details

From the project README

Jmeter Test Plan Creator

Overview

This skill provides automated assistance for jmeter test plan creator tasks within the Performance Testing domain.

When to Use

This skill activates automatically when you:

Mention "jmeter test plan creator" in your request
Ask about jmeter test plan creator patterns or best practices
Need help with performance testing skills covering load testing, stress testing, benchmarking, and performance monitoring.

Instructions

Provides step-by-step guidance for jmeter test plan creator
Follows industry best practices and patterns
Generates production-ready code and configurations
Validates outputs against common standards

Examples

Example: Basic Usage Request: "Help me with jmeter test plan creator" Result: Provides step-by-step guidance and generates appropriate configurations

Prerequisites

Relevant development environment configured
Access to necessary tools and services
Basic understanding of performance testing concepts

Output

Generated configurations and code
Best practice recommendations
Validation results

Error Handling

Error	Cause	Solution
Configuration invalid	Missing required fields	Check documentation for required parameters
Tool not found	Dependency not installed	Install required tools per prerequisites
Permission denied	Insufficient access	Verify credentials and permissions

Resources

Official documentation for related tools
Best practices guides
Community examples and tutorials

Related Skills

Part of the Performance Testing skill category. Tags: performance, load-testing, k6, jmeter, benchmarking

Comments

Markdown supported

Details

Author: jeremylongshore
Repository: jeremylongshore/tons-of-skills-marketplace
Category: Testing & quality
Installs: 104
GitHub stars: 2,885

Report

More skills

All skills

hyperframes-cli

github.com/heygen-com

1.3M

HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, compare, grade-compare, preview, play, render, publish, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (hyperframes lambda deploy / render / progress / destroy / policies / sites).

tdd

github.com/mattpocock

1.2M

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

anti-ui-slop

uizze.com

932.8k

Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".

diagnosing-bugs

github.com/mattpocock

856.9k

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.