blazemeter-troubleshooting
Comprehensive troubleshooting guide for BlazeMeter, covering API Monitoring, Performance Testing, general issues, integrations, and security. Use when troubleshooting for (1) API Monitoring issues (Radar Agent auth, SSL certificates, debug tests), (2) Performance Testing issues (high response time, 500 errors, partial load, tests not starting), (3) General issues (delete non-empty project, forbidden domains, Chrome Extension export failures), (4) Integration issues (New Relic reporting), (5) Security issues (Apache Log4j2 vulnerability), (6) Support requests and tickets, or any other troubleshooting tasks.
61
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./resources/skills/blazemeter-troubleshooting/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 skill description that clearly identifies its domain (BlazeMeter troubleshooting), lists specific concrete scenarios organized by category, and includes an explicit 'Use when' clause with detailed triggers. The description is comprehensive without being unnecessarily verbose, and the product-specific terminology makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions and scenarios: Radar Agent auth, SSL certificates, debug tests, high response time, 500 errors, partial load, tests not starting, delete non-empty project, forbidden domains, Chrome Extension export failures, New Relic reporting, Apache Log4j2 vulnerability, and support tickets. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive troubleshooting guide for BlazeMeter covering multiple categories) and 'when' (explicit 'Use when troubleshooting for...' clause with numbered trigger scenarios and a catch-all 'or any other troubleshooting tasks'). | 3 / 3 |
Trigger Term Quality | Includes many natural keywords users would actually say when seeking help: 'BlazeMeter', 'API Monitoring', 'Performance Testing', 'SSL certificates', '500 errors', 'high response time', 'tests not starting', 'Chrome Extension', 'New Relic', 'Apache Log4j2', 'troubleshooting', 'support requests'. These cover a wide range of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'BlazeMeter' and the detailed enumeration of specific issue categories and scenarios. This is unlikely to conflict with other skills unless there are multiple BlazeMeter-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a routing document to reference files, which is appropriate for its scope, but the body content itself is padded with unnecessary filler and generic advice. The MCP tools section adds some value with specific tool names and parameters, but the main troubleshooting guidance is too vague to be actionable on its own. The progressive disclosure is the strongest aspect, with clear categorization and well-signaled references.
Suggestions
Remove the verbose Overview section and 'When to Use Each Reference' section, which repeat information already conveyed by the reference file listings and their descriptions.
Replace the generic Quick Start with a concrete diagnostic decision tree or flowchart (e.g., 'If error contains 401 → see api-monitoring.md § Radar Agent Auth Fail').
Add a concrete MCP tool usage example with actual tool call syntax rather than just describing the workflow in prose.
Trim filler phrases like 'Effective troubleshooting requires systematic diagnosis and understanding of common issues and their solutions' that add no actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose with unnecessary filler. The overview restates the description, 'Quick Start' is generic and adds no real value, 'When to Use Each Reference' repeats what's already obvious from the reference file names, and phrases like 'Effective troubleshooting requires systematic diagnosis' are platitudes Claude doesn't need. | 1 / 3 |
Actionability | The MCP tools section provides some concrete guidance with specific tool names, actions, and required arguments. However, there are no executable code examples, no specific diagnostic commands, and the 'Quick Start' and troubleshooting steps are vague ('Check relevant reference', 'Apply solutions'). The actual troubleshooting content is deferred entirely to reference files. | 2 / 3 |
Workflow Clarity | The MCP tools example workflow provides a reasonable sequence of steps, but the main 'Quick Start' workflow is too generic to be useful ('Identify the issue', 'Apply solutions'). There are no validation checkpoints or feedback loops for error recovery in any workflow. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to specific troubleshooting domains. Each reference file is clearly labeled with its contents, and navigation is straightforward. The organization by category (API Monitoring, Performance, General, etc.) is logical. | 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.