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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill jmeter-test-plan-creatorActivation
22%This description is essentially a placeholder that relies entirely on the skill name rather than providing useful selection criteria. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The duplicated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific capabilities: 'Creates JMeter test plans including thread groups, HTTP samplers, assertions, listeners, and timers. Generates .jmx files for load and stress testing.'
Add explicit trigger guidance: 'Use when the user mentions JMeter, load testing, stress testing, performance testing scripts, .jmx files, or needs to simulate concurrent users.'
Include natural keyword variations users would say: 'load test', 'stress test', 'concurrent users', 'throughput testing', 'response time testing', 'JMX'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Jmeter Test Plan Creator' and 'Performance Testing' without describing any concrete actions. It doesn't explain what the skill actually does (e.g., creates thread groups, configures samplers, sets up assertions). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause. The 'Triggers on' section is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains 'jmeter test plan creator' (duplicated) and 'Performance Testing' as trigger terms. These are relevant but miss common variations users might say like 'load testing', 'stress test', 'JMX file', 'performance script', or 'benchmark'. | 2 / 3 |
Distinctiveness Conflict Risk | The JMeter-specific focus provides some distinctiveness from generic testing skills, but 'Performance Testing' is broad enough to potentially conflict with other performance-related skills (e.g., Gatling, k6, Locust). | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual JMeter content. It contains zero actionable information about creating test plans - no XML structure, no thread group configuration, no sampler examples, no assertions, nothing. The entire content could apply to any skill by replacing the keyword.
Suggestions
Add executable JMeter test plan XML snippets showing thread groups, HTTP samplers, and listeners configuration
Include a step-by-step workflow: 1) Define thread group parameters, 2) Add samplers, 3) Configure assertions, 4) Add listeners, 5) Validate with `jmeter -n -t plan.jmx`
Provide concrete examples for common scenarios (REST API load test, form submission stress test) with specific configuration values
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with JMeter-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever - no code, no commands, no JMeter-specific instructions, no XML snippets for test plans. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided. Creating JMeter test plans involves specific steps (thread groups, samplers, listeners, assertions) but none are mentioned. There's no sequence, no validation, no process at all. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no links to JMeter documentation or related files. It's neither a useful overview nor does it point anywhere useful. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.