blazemeter-recorders
Comprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder. Use when working with recorders for (1) Recording tests with Chrome Extension, (2) Creating and using Proxy Recorder, (3) Configuring browsers and devices for proxy recording, (4) Setting port ranges for proxy recorder, or any other recording tasks.
54
60%
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-recorders/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 follows the recommended pattern closely. It clearly identifies the domain (BlazeMeter Recorders), lists specific capabilities in a numbered format, and includes an explicit 'Use when' clause with natural trigger terms. The description uses third person voice appropriately and is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: recording tests with Chrome Extension, creating and using Proxy Recorder, configuring browsers and devices for proxy recording, and setting port ranges. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter Recorders including Chrome Extension and Proxy Recorder) and 'when' (explicit 'Use when' clause with four numbered trigger scenarios plus a catch-all for other recording tasks). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'BlazeMeter', 'Chrome Extension', 'Proxy Recorder', 'recording tests', 'port ranges', 'browsers and devices', 'proxy recording'. Good coverage of terms a user working with BlazeMeter recording would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to BlazeMeter Recorders with distinct triggers like 'Chrome Extension', 'Proxy Recorder', and 'port ranges'. Unlikely to conflict with other skills due to the narrow, well-defined domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is primarily a table of contents with verbose filler content. It lacks any concrete, executable instructions—no commands, no code, no configuration examples. The MCP Tools section adds bulk without actionable value, and the actual recording guidance is entirely deferred to reference files that cannot be verified.
Suggestions
Add concrete, executable quick-start examples for both Chrome Extension recording and Proxy Recorder setup (e.g., actual proxy configuration commands, specific browser settings steps)
Remove or drastically condense the MCP Tools section—the tool descriptions are generic and don't add actionable value beyond what Claude can infer from tool names and parameters
Remove the 'When to Use Each Reference' section as it merely restates information already present in the Reference Files section headings
Add at least one complete end-to-end example with specific configuration values (e.g., proxy port, certificate installation steps) rather than abstract workflow descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows. The MCP Tools section explains obvious concepts ('Monitor execution of recorded tests', 'Manage tests created from recordings programmatically') and the 'When to Use Each Reference' section restates what's already clear from the reference file descriptions. Much of the content describes rather than instructs. | 1 / 3 |
Actionability | There is no concrete, executable guidance anywhere in the skill. No actual recording steps, no commands, no code examples, no configuration snippets. The 'Example Workflow' is just a high-level description ('Record test using Chrome Extension or Proxy Recorder') with no specifics on how to actually do anything. Everything defers to reference files. | 1 / 3 |
Workflow Clarity | The example workflow provides a numbered sequence of steps, but they are vague and lack validation checkpoints. Steps like 'Record test using Chrome Extension or Proxy Recorder' and 'Export recorded script to BlazeMeter' give no detail on how to perform or verify these actions. The MCP tool usage steps are clearer but still lack error handling or validation. | 2 / 3 |
Progressive Disclosure | The skill does reference external files (chrome-extension.md, proxy-recorder.md) with clear topic descriptions, which is good structure. However, the SKILL.md itself contains too much inline content that is neither actionable nor a useful overview (the entire MCP Tools section is padded filler), and no bundle files were provided to verify the references actually exist or contain useful content. | 2 / 3 |
Total | 6 / 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.