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 skill description that follows the pattern of good examples in the rubric. It clearly identifies the product domain (BlazeMeter API Monitoring), lists specific capabilities in a numbered format, and includes an explicit 'Use when' clause with comprehensive trigger scenarios. The description uses third person voice appropriately and provides enough specificity to distinguish it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 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 handling (CSV, Data Entities), and advanced features (GraphQL, SOAP, file uploads, environments). | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter API Monitoring covering test creation, scripting, integrations, etc.) and 'when' with an explicit 'Use when working with API Monitoring tests for...' clause followed by a numbered list of specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'API Monitoring', 'BlazeMeter', 'Slack', 'PagerDuty', 'Datadog', 'GraphQL', 'SOAP', 'CSV', 'RBAC', 'notifications', 'file uploads', 'environments'. These cover a wide range of terms a user working with BlazeMeter API Monitoring would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to 'BlazeMeter API Monitoring' specifically, which is a distinct product niche. The named integrations and BlazeMeter-specific concepts (buckets, Data Entities) make it unlikely to conflict with generic API testing or monitoring 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 well as a navigational index with excellent progressive disclosure and concise organization, but it fails to provide any actionable content in the SKILL.md itself. There are no code examples, no concrete commands, and no actual workflows — it's purely a table of contents. Without bundle files to verify the referenced content exists, the skill body alone gives Claude no executable guidance for performing API Monitoring tasks.
Suggestions
Add a concrete Quick Start example showing an actual API Monitoring test creation workflow with specific steps, commands, or API calls — not just category labels.
Include at least one executable code snippet (e.g., a basic Post-response Script assertion or a test configuration JSON) so the SKILL.md provides immediate actionable value.
Transform the Quick Start into a sequenced workflow with validation checkpoints, e.g., '1. Create test → 2. Add steps → 3. Validate configuration → 4. Run test → 5. Check results'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized. It avoids explaining what API Monitoring is in unnecessary detail, assumes Claude's competence, and every section serves a clear navigational or organizational purpose. The 'When to Use Each Reference' section is slightly redundant given the reference file descriptions, but it's brief enough to be useful. | 3 / 3 |
Actionability | The skill body contains zero executable code, no concrete commands, no specific API calls, and no examples. It is entirely a table of contents pointing to reference files. Without the bundle files to verify those references contain actionable content, the SKILL.md itself provides only vague directional guidance ('Configure test steps, behaviors, and locations'). | 1 / 3 |
Workflow Clarity | There is no workflow described. The 'Quick Start' section is just a list of topic categories, not a sequenced process. There are no steps for creating a test, no validation checkpoints, and no feedback loops. For a skill covering test creation and configuration, the absence of any concrete workflow is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is excellently structured as a hub document with clear, well-signaled one-level-deep references to seven categorized reference files. Each reference has a descriptive label and a brief summary of its contents. The 'When to Use Each Reference' section provides additional navigation guidance. | 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
b76b703
- 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.