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 weak across all dimensions. It reads more like a metadata label than a functional description, providing no concrete actions, no natural trigger terms beyond the skill name repeated, and no explicit guidance on when Claude should select this skill. The only slight positive is the mention of 'JMeter' which provides some domain specificity.
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 about load testing, stress testing, performance benchmarks, JMeter configurations, .jmx files, or creating test plans for web application performance.'
Remove the duplicated trigger term and replace with diverse natural language variations users might actually say, such as 'load test', 'stress test', 'performance benchmark', 'JMX', 'concurrent users', 'throughput testing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (JMeter, Performance Testing) but does not describe any concrete actions. There are no specific capabilities listed like 'creates thread groups', 'configures samplers', or 'sets up assertions'. It merely states it is a 'Test Plan Creator' without elaborating on what that entails. | 1 / 3 |
Completeness | The 'what' is extremely vague (just 'Test Plan Creator') and there is no explicit 'when' clause. There is no 'Use when...' guidance. The description only states it 'auto-activates' and lists a category, which does not answer either question adequately. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'jmeter test plan creator' repeated twice. It misses natural variations users would say such as 'load test', 'performance test', 'stress test', 'JMX file', 'thread group', 'HTTP sampler', or 'benchmark'. The coverage of natural language terms is very poor. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'JMeter' specifically does provide some distinctiveness since it names a specific tool, which reduces conflict with generic testing or document skills. However, the lack of specific actions means it could still 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 shell—a template placeholder that contains no actual instructional content about creating JMeter test plans. It consists entirely of meta-descriptions about what the skill would do, without any executable code, JMeter XML examples, configuration guidance, or concrete steps. It provides zero value beyond what Claude already knows.
Suggestions
Add concrete, executable JMeter test plan XML snippets showing common configurations (e.g., HTTP Request sampler, Thread Group setup, listeners) that can be copy-pasted.
Define a clear step-by-step workflow for creating a test plan: e.g., 1) Define thread groups, 2) Add samplers, 3) Configure assertions, 4) Add listeners, 5) Validate with `jmeter -n -t plan.jmx -l results.jtl`.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task, and replace with actual instructional content.
Include at least one complete, minimal JMeter .jmx test plan example with explanation of key elements and parameters to customize.
| 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 how to actually create 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. The content only describes what the skill supposedly does without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequencing, no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-description with no meaningful structure, no references to detailed files, and no navigable sections containing actual 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
4dee593
- 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.