CtrlK
BlogDocsLog inGet started
Tessl Logo

blazemeter-getting-started

Getting started guides for BlazeMeter, including onboarding, migration guides, continuous testing journey, glossary, and mobile testing. Use when getting started with BlazeMeter for (1) Navigating BlazeMeter University onboarding, (2) Migrating from Runscope or JMeter, (3) Understanding the continuous testing journey, (4) Referencing BlazeMeter terminology, (5) Testing mobile sites and apps, or any other getting started tasks.

86

1.53x
Quality

83%

Does it follow best practices?

Impact

89%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

Well-structured content with concrete MCP tool guidance and excellent progressive disclosure via real reference files. The main weakness is redundancy between the Reference Files and When-to-Use sections that inflates token cost without adding clarity.

Suggestions

Merge 'When to Use Each Reference' into the Reference Files list so each entry carries its description and trigger in one place, removing the duplicated block.

Trim the generic 'When to Use MCP Tools' bullets (Account Setup, Learning) that restate the tool list above them, or replace them with concrete decision guidance.

Consider moving the detailed per-tool argument tables into a reference file, keeping SKILL.md to the example workflow and a compact tool summary.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but 'When to Use Each Reference' repeats the per-file descriptions already given in 'Reference Files', and the generic 'When to Use MCP Tools' bullets (Account Setup, Learning) add little — both could be tightened.

3 / 5

Actionability

Gives concrete MCP tool and action names with required arguments (e.g. `blazemeter_user` with action `read_user`) plus a numbered example workflow, though guidance is descriptive rather than copy-paste-ready code.

4 / 5

Workflow Clarity

The example workflow is a clear four-step sequence of real tool calls; being read-only exploration it needs no destructive-operation validation, so the absence of validation checkpoints is not penalized.

4 / 5

Progressive Disclosure

SKILL.md is an overview pointing to six real, one-level-deep reference files, each clearly signaled with a markdown link and a short description, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly pairs concrete capabilities with natural trigger phrasing and a clear when-to-use clause. The only weakness is the catch-all 'any other getting started tasks' that slightly dilutes distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete tasks — onboarding, migration from Runscope/JMeter, the continuous testing journey, glossary terminology, and mobile testing — giving comprehensive coverage of the getting-started domain.

5 / 5

Completeness

Clearly answers 'what' (getting started guides for BlazeMeter including the five areas) and 'when' via an explicit 'Use when getting started with BlazeMeter for (1)…(5)' trigger clause.

5 / 5

Trigger Term Quality

Uses natural phrases users would actually say — 'getting started with BlazeMeter', 'onboarding', 'migrating from Runscope or JMeter', 'testing mobile sites and apps' — with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Has a clear BlazeMeter-specific niche with distinct triggers, but the trailing 'or any other getting started tasks' broadens scope and introduces minor overlap risk with other getting-started skills.

4 / 5

Total

19

/

20

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: 6 missing, 6 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.