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.

88

1.60x
Quality

Does it follow best practices?

Impact

90%

1.60x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

A clean, well-organized index skill that excels at progressive disclosure and conciseness by routing to real reference files. Its weaknesses are that the body itself offers no executable code and only topical, non-sequenced workflow guidance.

Suggestions

Add at least one concrete, copy-paste-ready example (e.g., a minimal API test step or script snippet) in the Quick Start so the body is actionable without always opening a reference.

Reframe 'Quick Start' as a short ordered workflow (e.g., create test -> add steps -> add script -> configure notifications) with an explicit verification step such as running/previewing the test before saving.

DimensionReasoningScore

Conciseness

The body is a lean overview that points to reference files without explaining concepts Claude already knows; the only minor redundancy is restating the frontmatter summary, but every section earns its place.

3 / 3

Actionability

The body gives concrete routing guidance and topic-level pointers to specific reference files, but contains no executable code or commands itself; actionable detail lives in the references, so it stops short of copy-paste-ready instruction.

2 / 3

Workflow Clarity

A 'Quick Start' topic list and 'When to Use Each Reference' navigation aid provide useful routing, but these are topical categories rather than a sequenced multi-step process with checkpoints, and no validation steps are present.

2 / 3

Progressive Disclosure

The body is a concise overview pointing to seven one-level-deep reference files that all exist in ./references/, each clearly signaled with the topics it covers and paired with a '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.

A strong, well-structured description that clearly states capabilities and provides explicit, enumerated use-when triggers tied to natural user language. It is specific, complete, and distinct from other skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions across test creation, scripting (Initial, Pre-request, Post-response), integrations, RBAC, notifications, test data, and advanced features, matching the score-3 anchor for listing several specific actions.

3 / 3

Completeness

It explicitly answers both what the skill does and when to use it via a clear 'Use when working with API Monitoring tests for...' clause with enumerated triggers, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

It includes natural terms users would say ('API Monitoring', 'API tests', 'custom scripts', 'Slack', 'PagerDuty', 'Datadog', 'CSV', 'GraphQL', 'SOAP'), giving good coverage despite some jargon like 'Data Entities' and 'buckets'.

3 / 3

Distinctiveness Conflict Risk

'BlazeMeter API Monitoring' is a clear niche anchored by product-specific triggers (Slack, PagerDuty, Datadog) and format-specific terms (GraphQL, SOAP), 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.