CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized overview that leverages progressive disclosure effectively, with concrete MCP tool details and lean prose. Its weaknesses are in the recording workflow itself — the inline recording guidance is descriptive rather than actionable, and the workflow lacks validation checkpoints.

Suggestions

Add one or two concrete inline steps (or a minimal code/command snippet) for starting a recording in the Quick Start, so the primary task is actionable without requiring a reference file.

Tighten the Example Workflow by making the 'Export recorded script to BlazeMeter' step concrete (specific action/tool) and adding a verification checkpoint (e.g., confirm the recorded test appears via blazemeter_tests list before monitoring).

Reduce the mild redundancy between the Overview and Quick Start sections, which restate the same three recording options.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a proxy or browser extension is, and each section earns its place; only mild Overview/Quick-Start redundancy keeps it from being perfectly tight.

3 / 3

Actionability

MCP tool guidance is concrete (tool names, actions, required args, return values), but the core recording instructions are delegated to references and the Quick Start is descriptive ('Record tests directly from Chrome browser') rather than executable, leaving the body's primary task incomplete.

2 / 3

Workflow Clarity

The Example Workflow gives a clear numbered sequence (record → export → list → read → monitor), but there are no validation checkpoints and the early steps ('Export recorded script to BlazeMeter') are vague; not above 2 because no explicit verification or error-recovery step is present.

2 / 3

Progressive Disclosure

A clear overview points to two well-signaled, one-level-deep references (chrome-extension.md, proxy-recorder.md — both verified present) with section-level summaries and a 'When to Use Each Reference' guide, matching the clean split anchor.

3 / 3

Total

10

/

12

Passed

Description

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.

The description is a strong, complete trigger: it names the domain, lists four concrete capabilities, and gives an explicit 'Use when' clause with enumerated triggers. It is concise, in third person, and clearly niche-scoped to BlazeMeter recorders.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'Recording tests with Chrome Extension', 'Creating and using Proxy Recorder', 'Configuring browsers and devices for proxy recording', 'Setting port ranges' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly states what ('Comprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder') and when ('Use when working with recorders for (1)...(4)..., or any other recording tasks').

3 / 3

Trigger Term Quality

Uses natural terms a user would say — 'recorders', 'Chrome Extension', 'Proxy Recorder', 'proxy recording', 'port ranges' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to BlazeMeter Recorders with distinct recorder-centric triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing, 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
Blazemeter/bzm-mcp
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.