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 severely lacking in detail and actionability. It essentially just names the skill and its category without describing any concrete capabilities, use cases, or trigger conditions. The repeated trigger term and absence of a 'Use when...' clause make it very difficult for Claude to appropriately select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates JMeter test plans (.jmx files) with thread groups, HTTP samplers, listeners, assertions, and timers for load and stress testing.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a JMeter test plan, set up load testing, configure performance tests, or generate .jmx files.'
Include natural trigger term variations users would say: 'load test', 'stress test', 'performance test', 'JMX', '.jmx file', 'thread group', 'HTTP request sampler', 'JMeter script'.
| 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 only says 'Auto-activating skill for Performance Testing' which is vague. | 1 / 3 |
Completeness | The 'what' is extremely weak — it only says it's a 'Jmeter Test Plan Creator' without explaining what that entails. 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', 'HTTP sampler', '.jmx', or 'create a test plan'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'JMeter' specifically does provide some distinctiveness since JMeter is a specific tool, which reduces conflict with generic testing or coding skills. However, the vague 'Performance Testing' category could overlap with other performance testing tools like Gatling or k6. | 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 repeatedly names the skill ('jmeter test plan creator') without providing any actionable instructions, JMeter test plan XML examples, configuration guidance, or workflow steps. It would provide zero value to Claude beyond what it already knows.
Suggestions
Add concrete, executable JMeter test plan XML snippets showing thread groups, samplers, listeners, and assertions for common scenarios (e.g., HTTP load test).
Define a clear step-by-step workflow: identify endpoints → configure thread groups → add samplers → set assertions → run and validate results, with specific commands (e.g., `jmeter -n -t plan.jmx -l results.jtl`).
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than teaching how to create test plans.
Include at least one complete, copy-paste-ready JMeter test plan example with parameterized values and explain key configuration knobs (ramp-up, duration, thread count).
| 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. There are no steps, no sequencing, no validation checkpoints. The 'step-by-step guidance' is merely claimed in the Capabilities section but never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no meaningful structure, no references to detailed materials, and no actionable sections. The headings exist but contain only generic placeholder text. | 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
700215b
- 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.