Name: blazemeter-api-reference
Rating: 61.6 (1 reviews)
Author: Blazemeter

blazemeter-api-reference

Comprehensive reference for BlazeMeter REST APIs, including authentication, identifiers, and API endpoints. Use when working with BlazeMeter APIs for (1) Understanding BlazeMeter REST API structure, (2) Authenticating API requests, (3) Obtaining identifiers (Workspace ID, Project ID, Test ID, etc.), (4) Using Test Data API, (5) Using Cloning API, (6) Using Export API, (7) Using Service Virtualization Bulk Operations APIs, or any other API tasks.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/blazemeter-api-reference/SKILL.md

Quality

Content

53%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.

The body is a well-structured index to real, one-level-deep reference files, and the MCP tool catalog is unusually concrete. However, it carries redundant overview/quick-start/when-to-use sections, no executable REST example for the skill's core claim, and no validation or error-recovery guidance in its workflows.

Suggestions

Consolidate 'Reference Files' and 'When to Use Each Reference' into a single section (file link plus its trigger condition) to remove the duplicated guidance.

Add one executable REST example inline (e.g., a curl request authenticating with an API key and listing tests) so the core API workflow is actionable without opening a reference file.

Move the detailed MCP tools catalog into its own reference file (e.g., references/mcp-tools.md) and keep only the MCP-vs-REST comparison and example workflow in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but has redundant sections: the opening line 'Comprehensive reference for BlazeMeter REST APIs.' repeats the description, 'Quick Start' restates the 'Overview' topics, and 'When to Use Each Reference' duplicates the per-file descriptions already given in 'Reference Files'.	3 / 5
Actionability	The MCP tools section is genuinely concrete (tool names, actions, required args like '`blazemeter_execution` with action `start`', 'Required args: `test_id` (integer)'), but the skill's core purpose — REST API usage — has no executable example inline (no curl or API-key request sample); those details are entirely deferred to reference files.	3 / 5
Workflow Clarity	The 'Example Workflow' gives a clear 4-step sequence with concrete tool calls, but there are no validation checkpoints or error-recovery guidance, and 'Quick Start' lists topics rather than actionable steps.	3 / 5
Progressive Disclosure	All seven referenced files exist, are one level deep, and are well-signaled with descriptions; the body serves as an overview pointing to them. It falls short of 5 because the ~60-line MCP tools catalog is inline content that would fit better in its own reference file.	4 / 5
	Total	13 / 20 Passed

Description

92%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: concrete, comprehensive capability list paired with an explicit 'Use when...' clause covering seven enumerated use cases plus a catch-all. Only minor gap is the absence of a few natural trigger synonyms such as 'API key' or 'load testing'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Authenticating API requests', 'Obtaining identifiers (Workspace ID, Project ID, Test ID, etc.)', 'Using Test Data API', 'Using Cloning API', 'Using Export API', 'Using Service Virtualization Bulk Operations APIs' — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	It explicitly answers both what ('Comprehensive reference for BlazeMeter REST APIs, including authentication, identifiers, and API endpoints') and when ('Use when working with BlazeMeter APIs for (1)... (7)..., or any other API tasks') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-keyword coverage ('BlazeMeter', 'REST APIs', 'Workspace ID', 'Test Data API', 'Service Virtualization'), but common variations a user might say — 'API key', 'run tests', 'load testing' — are missing, so it does not reach the comprehensive-with-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	'BlazeMeter' names a clear niche with distinct triggers (specific named APIs, identifier lookups); minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 7 missing, 7 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: Blazemeter/bzm-mcp
Path: resources/skills/blazemeter-api-reference/SKILL.md
Commit: cfb1f58

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.