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.
80
72%
Does it follow best practices?
Impact
90%
1.60xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./resources/skills/blazemeter-api-monitoring/SKILL.mdQuality
Discovery
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.
This is a strong, well-structured description that follows the pattern of good examples in the rubric. It clearly identifies the product domain (BlazeMeter API Monitoring), lists specific concrete capabilities in a numbered format, and includes an explicit 'Use when' clause with comprehensive trigger scenarios. The description is rich in natural trigger terms and highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: test creation, configuration, scripting (Initial, Pre-request, Post-response), integrations with named services (Slack, PagerDuty, Datadog), managing teams/buckets/RBAC, notifications, test data (CSV, Data Entities), and advanced features (GraphQL, SOAP, file uploads, environments). | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter API Monitoring with specific capabilities listed) and 'when' (explicit 'Use when working with API Monitoring tests for...' clause with numbered trigger scenarios and a catch-all 'or any other API Monitoring tasks'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'API Monitoring', 'API tests', 'Slack', 'PagerDuty', 'Datadog', 'GraphQL', 'SOAP', 'CSV', 'RBAC', 'BlazeMeter', 'notifications', 'file uploads', 'environments'. Good coverage of terms a user working with BlazeMeter API Monitoring would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'BlazeMeter' and the focused domain of 'API Monitoring'. The named integrations and specific scripting types (Initial, Pre-request, Post-response) further narrow the niche, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions purely as a navigation hub/table of contents for reference files, which it does well with clear organization and appropriate progressive disclosure. However, it critically lacks any actionable content—no code examples, no concrete commands, no executable guidance—making it essentially useless without the bundle files. The 'Quick Start' section is misleadingly named as it provides no actual quick-start instructions.
Suggestions
Add a genuine Quick Start section with at least one concrete, executable example (e.g., a minimal API test creation workflow with actual API calls or UI steps)
Include at least one representative code snippet for scripting (e.g., a basic Post-response assertion script) so the skill body itself provides actionable value
Transform the Quick Start into an actual workflow with numbered steps showing how to create and run a basic API monitoring test, including validation of results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It avoids explaining what APIs are, what BlazeMeter is, or other concepts Claude already knows. Every section serves a clear navigational or organizational purpose with no padding. | 3 / 3 |
Actionability | The skill provides no concrete code, commands, API calls, or executable examples. It is entirely a table of contents pointing to reference files, with no actionable guidance in the body itself. The 'Quick Start' section is just a list of categories, not actual steps. | 1 / 3 |
Workflow Clarity | There are no workflows, sequences, or step-by-step processes described. The 'Quick Start' is a categorized list, not a workflow. There are no validation checkpoints or feedback loops for any operations. | 1 / 3 |
Progressive Disclosure | The content is well-organized as a hub document with clear one-level-deep references to seven categorized reference files. The 'When to Use Each Reference' section provides excellent navigation guidance. References are clearly signaled with descriptive summaries. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Blazemeter/bzm-mcp
- Commit
6395eba
- 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.