CtrlK
BlogDocsLog inGet started
Tessl Logo

blazemeter-api-monitoring

Comprehensive guide for BlazeMeter API Monitoring, including test creation, configuration, scripting, integrations, notifications, and management. Use when working with API Monitoring tests for (1) Creating and configuring API tests, (2) Writing custom scripts (Initial, Pre-request, Post-response), (3) Integrating with third-party services (Slack, PagerDuty, Datadog, etc.), (4) Managing teams, buckets, and RBAC, (5) Configuring notifications and sharing results, (6) Using test data (CSV, Data Entities), (7) Advanced features (GraphQL, SOAP, file uploads, environments), or any other API Monitoring tasks.

87

1.60x
Quality

85%

Does it follow best practices?

Impact

90%

1.60x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-structured index-style SKILL.md that excels at progressive disclosure by routing to verified reference files, but it offers only navigational guidance with no inline executable steps and carries minor redundancy between its two reference-routing sections.

Suggestions

Merge 'Reference Files' and 'When to Use Each Reference' into a single table (file → topics → when-to-use) to remove redundancy and tighten the token budget.

Add one or two concrete inline examples (e.g., a minimal Pre-request script snippet or a test-creation API call) so the body is actionable without forcing a reference read for common cases.

Clarify category boundaries in the routing guide (e.g., note that environments/scheduling live in configuration.md) so Claude can disambiguate when a task spans two categories.

DimensionReasoningScore

Conciseness

The body is a lean overview/index that assumes Claude's competence and avoids explaining known concepts, but the 'Reference Files' and 'When to Use Each Reference' sections overlap noticeably and could be merged into a single routing table.

4 / 5

Actionability

Guidance is navigational rather than executable: it tells Claude which reference file to consult per task but provides no inline commands, code, or concrete procedural steps in the body itself.

3 / 5

Workflow Clarity

The single routing action ('pick the right reference') is unambiguous thanks to the 'When to Use Each Reference' mapping, with no destructive/batch operations that would require validation checkpoints; minor ambiguity remains at category boundaries.

4 / 5

Progressive Disclosure

Clear overview pointing to seven well-signaled one-level-deep references, all of which exist as real files in references/, with content appropriately split and easy navigation via both a file listing and a usage map.

5 / 5

Total

16

/

20

Passed

Description

100%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, third-person description that clearly states capabilities and provides an explicit, enumerated 'Use when...' trigger clause covering the full API Monitoring domain. It is comprehensive, concrete, and distinctive with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full API Monitoring surface (test creation/configuration, Initial/Pre-request/Post-response scripts, third-party integrations, teams/buckets/RBAC, notifications, CSV/Data Entities, GraphQL/SOAP/file uploads/environments), giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' ('Comprehensive guide for BlazeMeter API Monitoring, including test creation, configuration, scripting, integrations, notifications, and management') and 'when' ('Use when working with API Monitoring tests for (1)...(7)...') with concrete numbered trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would actually say ('Creating and configuring API tests', 'Writing custom scripts', 'Integrating with third-party services (Slack, PagerDuty, Datadog)', 'GraphQL, SOAP, file uploads') plus concrete product names and feature synonyms.

5 / 5

Distinctiveness Conflict Risk

Targets a specific named product niche ('BlazeMeter API Monitoring') with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

20

/

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: 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.