CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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-structured API overview with strong progressive disclosure and concrete actionable tool/endpoint guidance. Its main weaknesses are some repeated verbosity across MCP tool categories and the absence of validation checkpoints for batch operations.

Suggestions

Add explicit validation or verification steps for bulk/batch operations (e.g., confirm counts before/after, check API response status) to raise workflow clarity.

Tighten the MCP tools section by consolidating the repeated 'Required args' pattern into a shared note, and remove the duplicative 'When to Use Each Reference' section since the Reference Files list already conveys this.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the per-category MCP tool listings repeat a 'Required args' pattern across many categories and the 'When to Use Each Reference' section largely restates the Reference Files section, so it could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: specific tool names with named actions (e.g., 'blazemeter_execution with action start'), required args, REST equivalents, and a numbered example workflow.

3 / 3

Workflow Clarity

Quick Start and the example workflow are sequenced, but the skill covers Service Virtualization Bulk Operations (a batch context) with no validation or verification checkpoints, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep references to verified files (overview.md, authentication.md, identifiers.md, etc.) and an organized 'When to Use' navigation aid.

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 specific, complete, and well-triggered, concisely stating both capabilities and explicit 'Use when' conditions. It is a strong, distinctive description with no notable weaknesses.

DimensionReasoningScore

Specificity

Enumerates 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'), matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

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...'), matching the top anchor with explicit triggers.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('BlazeMeter APIs', 'authenticating API requests', 'Workspace ID', 'Project ID', 'Test ID', 'Test Data API', 'Cloning API', 'Export API'), giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear BlazeMeter-specific niche with distinct triggers (named APIs and identifiers), 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: 7 missing, 7 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.