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 defines its scope, provides extensive trigger terms, and explicitly states when it should be used. The enumerated categories with specific examples make it easy for Claude to match user requests to this skill. The description uses proper third-person voice and avoids vague language.
| 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 detailed numbered trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes many natural keywords users would actually say when troubleshooting BlazeMeter: 'API Monitoring', 'Performance Testing', 'SSL certificates', '500 errors', 'high response time', 'Chrome Extension', 'New Relic', 'Log4j2', 'support tickets'. 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 types. Unlikely to conflict with other skills given the narrow, well-defined domain. | 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.
The skill's strongest aspect is its progressive disclosure structure, with well-organized references to topic-specific files. However, the main body is padded with generic advice and explanations that don't add value for Claude. The actionability is moderate—MCP tool details are helpful but the core troubleshooting guidance is entirely deferred to reference files without any concrete examples in the main skill.
Suggestions
Remove the generic Quick Start section and the Overview paragraph—they state obvious troubleshooting methodology that Claude already knows.
Eliminate the 'When to Use Each Reference' section, which largely duplicates the information already in the Reference Files section headings and descriptions.
Add at least one concrete, executable MCP tool invocation example instead of describing the workflow abstractly (e.g., show actual tool call syntax with sample parameters).
Trim the MCP Tools section by removing the 'When to Use MCP Tools' subsection, which restates obvious use cases like 'use for execution analysis' and 'use for monitoring'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with unnecessary filler. The overview restates the description, the 'Quick Start' is generic advice Claude already knows ('identify the issue', 'apply solutions'), and the 'When to Use Each Reference' section largely repeats the reference file listing. Phrases like 'Effective troubleshooting requires systematic diagnosis' add no value. | 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 commands, and the troubleshooting steps themselves are vague ('follow diagnostic steps and solutions'). The actual actionable content is deferred entirely to reference files. | 2 / 3 |
Workflow Clarity | The Quick Start provides a basic sequence but it's generic and lacks validation checkpoints. The MCP example workflow has numbered steps but no error handling or feedback loops. For a troubleshooting skill that may involve destructive operations (like deleting projects), there are no validation or verification steps mentioned. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to specific topic files. Each reference file is clearly labeled with its contents, and the navigation is straightforward. The categorization into API Monitoring, Performance, General, Integrations, and Security 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
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.