blazemeter-performance-testing
Comprehensive guide for BlazeMeter Performance Testing, including load configuration, reporting, JMeter configuration, Taurus, scenarios, and advanced features. Use when working with Performance tests for (1) Configuring load settings and distribution, (2) Creating and running tests (JMeter, Browser, URL/API, Multi-Test), (3) Analyzing reports and filtering data, (4) Configuring JMeter properties and scenarios, (5) Using Taurus for test configuration, (6) Advanced features (AI Log Analysis, APM Integration, Network Emulation, Mainframe Testing), (7) Troubleshooting test issues, or any other Performance Testing tasks.
61
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./resources/skills/blazemeter-performance-testing/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly identifies the tool domain (BlazeMeter), lists specific capabilities across multiple areas, and provides explicit trigger guidance with a numbered list of use cases. The description follows the pattern of good examples in the rubric, with concrete actions and a well-structured 'Use when' clause. Minor improvement could be made by being slightly more concise, but the detail level is appropriate for distinguishing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: configuring load settings, creating/running tests (with specific types), analyzing reports, configuring JMeter properties, using Taurus, and advanced features like AI Log Analysis, APM Integration, Network Emulation, and Mainframe Testing. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter performance testing with specific capabilities listed) and 'when' (explicit 'Use when working with Performance tests for...' clause with seven numbered trigger scenarios plus a catch-all). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BlazeMeter', 'Performance Testing', 'load', 'JMeter', 'Taurus', 'reports', 'URL/API', 'Network Emulation', 'Mainframe Testing', 'APM Integration'. These cover a wide range of terms a user working with performance testing would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool focus on BlazeMeter, JMeter, and Taurus. The combination of these specific product names and performance testing domain makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured as a navigation hub with clear progressive disclosure to reference files, but suffers from significant verbosity and redundancy. Multiple sections restate the same information (e.g., 'When to Use Each Reference' duplicates the Reference Files section). The actionability is moderate—MCP tool names are specific but lack concrete examples with parameters, payloads, or expected responses.
Suggestions
Remove the redundant 'When to Use Each Reference' and 'When to Use MCP Tools' sections, as they restate information already present in the Reference Files and Available MCP Tools sections.
Add concrete MCP tool invocation examples with actual parameters (e.g., specific test_id values, JSON request/response snippets) to make the workflows copy-paste actionable.
Add validation checkpoints to the example workflows, such as checking execution status before reading results, or verifying load configuration was applied correctly.
Trim the 'Quick Start' section to either be genuinely actionable (e.g., a minimal end-to-end example) or remove it since it's just a table of contents that duplicates the document structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and repetitive. The 'When to Use MCP Tools' section restates what the tool list already implies. The 'When to Use Each Reference' section at the bottom repeats what the Reference Files section already conveys. The 'Quick Start' section is just a table of contents, not actionable. Multiple sections explain obvious things Claude would already know. | 1 / 3 |
Actionability | The MCP tool names and actions are concrete and specific, and the example workflows provide step-by-step sequences. However, there are no actual executable code examples, no concrete parameter values, no JSON payloads or response schemas shown. The guidance stays at the level of 'use tool X with action Y' without showing what the actual invocations look like. | 2 / 3 |
Workflow Clarity | The example workflows provide clear sequential steps for creating/running tests and analyzing results. However, there are no validation checkpoints, no error handling guidance, no feedback loops (e.g., what to do if execution fails or if load configuration is rejected). For operations that could fail, this is a notable gap. | 2 / 3 |
Progressive Disclosure | The skill has a clear overview structure with well-organized, one-level-deep references to specific topic files. Each reference file is clearly labeled with its contents, and the navigation is straightforward with descriptive links grouped by category. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Blazemeter/bzm-mcp
- Commit
b76b703
- 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.