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.

84

1.60x
Quality

80%

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

72%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 lean, well-organized index-style SKILL.md that excels at progressive disclosure: seven accurate, clearly-annotated reference links with task-based routing. Its weaknesses are the absence of any worked example or concrete quick-start step, and a Quick Start that reads as a feature list rather than an actionable sequence.

Suggestions

Replace the vague 'Quick Start' bullets with one concrete worked example (e.g., a minimal API test creation step or a short Pre-request Script snippet) so the body has executable guidance before deferring to references.

Merge the 'Reference Files' topic lists and the 'When to Use Each Reference' section into a single table (reference file | topics | when to use) to eliminate duplicated routing information.

Cut the 'Overview' paragraph that restates the frontmatter description, keeping only the one-line product framing.

DimensionReasoningScore

Conciseness

The ~50-line body is efficient with no padding or basic-concept explanations, but the Overview repeats the frontmatter description and the 'When to Use Each Reference' section partially duplicates the 'Reference Files' topic lists — minor trimming is possible, matching the 4-anchor's 'minor instances of over-explanation'.

4 / 5

Actionability

As an instruction-only navigation skill, its guidance is concrete — each of the 7 sections names a specific reference file with its exact topics, and 'When to Use Each Reference' maps tasks to files — but the 'Quick Start' bullets ('Configure test steps, behaviors, and locations') stop short of one worked example, leaving minor gaps versus the 5-anchor.

4 / 5

Workflow Clarity

The 'Quick Start' items are capability areas rather than a sequenced workflow, and no validation checkpoints or task sequences are given; steps exist but are coarse and checkpoint-free, fitting the 3-anchor. No destructive/batch operations are involved, so no lower cap applies.

3 / 5

Progressive Disclosure

The body is a clean overview pointing to seven well-signaled, one-level-deep reference files, all of which exist in references/ and match their link paths exactly, plus a routing section ('When to Use Each Reference') for navigation — squarely the 5-anchor.

5 / 5

Total

16

/

20

Passed

Description

88%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, well-structured description: third-person voice, concrete enumerated capabilities, and an explicit multi-clause 'Use when...' trigger section covering the skill's full feature surface. The only gaps are a few missing natural synonyms and slight generic phrasing around API test creation.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions across seven enumerated areas — 'Creating and configuring API tests', 'Writing custom scripts (Initial, Pre-request, Post-response)', 'Integrating with third-party services (Slack, PagerDuty, Datadog)', 'Managing teams, buckets, and RBAC' — giving comprehensive coverage rather than the minor gaps of the 4-anchor.

5 / 5

Completeness

It clearly answers both: 'Comprehensive guide for BlazeMeter API Monitoring, including test creation, configuration, scripting, integrations, notifications, and management' (what) and an explicit 'Use when working with API Monitoring tests for (1)...(7), or any other API Monitoring tasks' (when) with concrete trigger phrases, matching the 5-anchor exemplar format.

5 / 5

Trigger Term Quality

Good keyword coverage including natural terms like 'API Monitoring', 'API tests', 'Slack, PagerDuty, Datadog', 'CSV', 'GraphQL, SOAP', and 'RBAC', but a few common synonyms users might say (e.g. 'synthetic monitoring', 'uptime/health checks') are missing, so it falls short of the 5-anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The product-specific 'BlazeMeter API Monitoring' framing gives it a clear niche with distinct triggers, but phrases like 'Creating and configuring API tests' carry minor overlap risk with generic API-testing skills, placing it just below the 5-anchor's minimal conflict risk.

4 / 5

Total

18

/

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.

Validation — 15 / 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.