blazemeter-scripting
Comprehensive guide for BlazeMeter Scripting, including Groovy/Beanshell, JMeter plugins, JMeter DSL, and API Monitoring scripting. Use when working with scripting for (1) Writing files in Groovy/Beanshell scripts, (2) Using non-standard JMeter plugins, (3) Creating JMeter tests with JMeter DSL, (4) Writing custom scripts for API Monitoring (custom libraries, included libraries, initial script, reusable snippets), or any other scripting 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-scripting/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 defines its scope around BlazeMeter scripting with specific sub-domains, includes natural trigger terms that users in this space would use, and provides explicit 'Use when' guidance with enumerated scenarios. The description follows the pattern of good examples in the rubric, using third person voice and providing both what and when information concisely.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing files in Groovy/Beanshell scripts, using non-standard JMeter plugins, creating JMeter tests with JMeter DSL, writing custom scripts for API Monitoring with sub-categories (custom libraries, included libraries, initial script, reusable snippets). | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter Scripting covering Groovy/Beanshell, JMeter plugins, JMeter DSL, API Monitoring scripting) and 'when' (explicit 'Use when working with scripting for...' clause with four numbered trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BlazeMeter', 'Groovy', 'Beanshell', 'JMeter plugins', 'JMeter DSL', 'API Monitoring', 'scripting', 'custom libraries', 'reusable snippets'. These cover the domain-specific terms a user working in this space would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around BlazeMeter scripting specifically. The combination of BlazeMeter, JMeter DSL, Groovy/Beanshell, and API Monitoring scripting creates a very specific domain that is 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.
This skill functions primarily as a routing/index document, pointing to reference files for actual scripting details. While the progressive disclosure structure is good, the main content lacks any concrete, executable examples or actionable guidance — it describes what can be done without showing how. The MCP Tools section adds some specificity but is verbose relative to its value.
Suggestions
Add at least one concrete, executable code example per scripting type (Groovy snippet, JMeter DSL snippet, API Monitoring JS snippet) in the Quick Start section to make the skill immediately actionable.
Remove the 'When to Use Each Reference' section as it duplicates the Quick Start and reference file descriptions, improving conciseness.
Add a validation or troubleshooting step to the Example Workflow, such as how to verify a script is correctly configured or how to diagnose script-related execution failures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary repetition — the 'When to Use Each Reference' section largely duplicates the Quick Start section and the reference file descriptions. The MCP Tools section is somewhat verbose with information Claude could infer, but it does provide specific tool names and arguments. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, and no specific examples of actual scripting. It's essentially a table of contents with vague descriptions like 'Write files and custom logic' and 'Use non-standard JMeter plugins' without any concrete guidance on how to do these things. | 1 / 3 |
Workflow Clarity | The 'Example Workflow' section provides a numbered sequence for managing scripted tests, but it lacks validation checkpoints and error recovery steps. The workflow is more of a description of tool usage than a clear operational process with feedback loops. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to four specific reference files. Each reference is clearly signaled with descriptive labels indicating what content it contains, and navigation is straightforward. | 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.