jmeter-test-plan-creator
Jmeter Test Plan Creator - Auto-activating skill for Performance Testing. Triggers on: jmeter test plan creator, jmeter test plan creator Part of the Performance Testing skill category.
35
3%
Does it follow best practices?
Impact
94%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/jmeter-test-plan-creator/SKILL.mdQuality
Discovery
7%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 description is extremely thin—it essentially just restates the skill name without describing what the skill actually does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it very difficult for Claude to reliably select this skill from a pool of available options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates JMeter .jmx test plans with thread groups, HTTP samplers, listeners, assertions, and timers for load and stress testing.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a JMeter test plan, build a load test, generate a .jmx file, set up performance testing, or configure stress tests.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'load test', 'stress test', 'JMX', 'performance test plan', 'throughput testing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('JMeter test plan') and the category ('Performance Testing') but does not describe any concrete actions. There are no specific capabilities listed like 'creates thread groups, configures samplers, sets up assertions'. | 1 / 3 |
Completeness | The 'what' is extremely vague (just 'Jmeter Test Plan Creator') with no elaboration on capabilities, and the 'when' is missing entirely—there is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'jmeter test plan creator' repeated twice. It misses natural variations users would say like 'load test', 'performance test', 'JMX file', 'stress test', 'thread group', or 'HTTP sampler'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'JMeter' specifically does provide some distinctiveness from generic performance testing or other load testing tools, but the lack of specific actions and the broad 'Performance Testing' category label could cause overlap with other performance testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It contains only boilerplate section headers and generic descriptions that repeat the skill name without providing any actionable guidance on creating JMeter test plans. It fails on every dimension because it teaches Claude nothing it doesn't already know and provides no concrete, executable instructions.
Suggestions
Add a concrete JMeter test plan XML example showing a basic HTTP request sampler with thread group configuration that Claude can use as a template.
Include a step-by-step workflow for creating a test plan: define thread groups → add samplers → configure listeners → add assertions → validate and run, with specific JMeter CLI commands (e.g., `jmeter -n -t testplan.jmx -l results.jtl`).
Provide specific configuration patterns for common scenarios (e.g., REST API load test, ramp-up strategy, think times) with executable XML snippets rather than vague descriptions.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers) that contain no substantive information and replace with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'jmeter test plan creator' excessively, and provides zero substantive information about actually creating JMeter test plans. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no JMeter XML snippets, no configuration examples, no specific steps for creating a test plan. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no meaningful structure. There are no references to detailed files, no examples section, and the headers contain only generic placeholder text rather than organized, navigable content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.