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). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BlazeMeter', 'Chrome Extension', 'Proxy Recorder', 'recording tests', 'port ranges', 'browsers and devices', 'proxy recording'. These cover the domain well and match natural user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product names (BlazeMeter, Chrome Extension, Proxy Recorder) and domain-specific terms (port ranges, proxy recording). Unlikely to conflict with other skills due to the narrow, well-defined niche. | 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 functions primarily as a table of contents with a verbose MCP tools section, but lacks any concrete, actionable content. It explains obvious concepts, provides no executable code or specific commands, and defers all real instruction to reference files. The MCP tools section, while structured, describes capabilities at a level Claude already understands rather than providing specific, copy-paste-ready guidance.
Suggestions
Remove or drastically condense the MCP Tools section — the tool descriptions repeat what Claude can infer from tool names and parameters. Replace with a brief table or one-liner per tool.
Add concrete, actionable quick-start steps for both Chrome Extension and Proxy Recorder directly in the skill body (e.g., specific proxy configuration commands, port settings, or Chrome extension setup steps).
Include at least one executable example, such as a specific proxy configuration snippet or a concrete MCP tool invocation with realistic parameters and expected output.
Remove the 'When to Use Each Reference' section — it restates information already conveyed by the reference file descriptions above it.
| 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 configuration snippets, no code examples. The 'Example Workflow' is a high-level description ('Record test using Chrome Extension or Proxy Recorder') rather than actionable instructions. Everything defers to reference files. | 1 / 3 |
Workflow Clarity | The example workflow provides a numbered sequence for managing recorded tests, but it lacks validation checkpoints and concrete details. Steps like 'Record test using Chrome Extension or Proxy Recorder' and 'Export recorded script to BlazeMeter' are vague with no verification steps or error recovery guidance. | 2 / 3 |
Progressive Disclosure | The skill does reference two external files with clear topic descriptions, which is good structure. However, without bundle files to verify the references exist, and given that the main body contains a large MCP Tools section that could arguably be its own reference, the organization is only partially effective. The reference links are well-signaled but the inline content bloat undermines the overview purpose. | 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
6395eba
- 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.