CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/blazemeter-troubleshooting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured overview with excellent progressive disclosure and a concrete MCP-tools section, but the body's own troubleshooting guidance is thin and generic, leaning on pointers while adding some redundant and padded prose.

Suggestions

Remove the generic "When to Use Each Reference" section (it duplicates the Reference Files list) and the filler sentence about systematic diagnosis to tighten the body.

Add a brief validation/checkpoint step to the Quick Start (e.g. "confirm the symptom matches a reference entry before applying solutions; if multiple match, narrow by checking execution status via blazemeter_execution") to give the workflow a real feedback loop.

Inline one or two concrete diagnostic snippets (e.g. the exact blazemeter_execution read call with a sample execution_id) so the body is actionable on its own rather than only pointing to references.

DimensionReasoningScore

Conciseness

Mostly efficient, but includes unnecessary filler ("Effective troubleshooting requires systematic diagnosis and understanding of common issues and their solutions") and a "When to Use Each Reference" section that largely duplicates the preceding "Reference Files" list, so it could be tightened.

3 / 5

Actionability

The MCP tools section gives concrete, executable guidance (tool names, actions, required args, returns), but the core troubleshooting solutions are deferred entirely to reference files and the Quick Start steps ("Apply solutions: Follow diagnostic steps and solutions") are high-level hints rather than executable instruction.

3 / 5

Workflow Clarity

A clear 4-step Quick Start sequence and a sequenced MCP example workflow are present, but there are no validation or checkpoint steps for confirming a diagnosis before escalating, and no feedback loop (diagnose → verify → retry) for the diagnostic process.

3 / 5

Progressive Disclosure

The body is a clean overview pointing to five real, one-level-deep reference files, each linked and summarized by topic (e.g. "[performance.md](...): High Response Time, 500 Response..."), with well-organized sections and easy navigation, matching the top anchor.

5 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 answers both what the skill does and when to use it, with concrete product-specific triggers. Its only weakness is the generic catch-all clause and the lack of synonym/extension coverage.

DimensionReasoningScore

Specificity

Names the BlazeMeter troubleshooting domain and enumerates many concrete issue types ("Radar Agent auth, SSL certificates", "high response time, 500 errors", "Apache Log4j2 vulnerability"), but the skill's action itself is the singular verb "troubleshooting" rather than a list of distinct actions, leaving a minor coverage gap relative to the top anchor.

4 / 5

Completeness

Explicitly states what it does ("Comprehensive troubleshooting guide for BlazeMeter, covering...") and provides a detailed numbered "Use when troubleshooting for (1)...(6)" clause with concrete trigger phrases, clearly matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural product-specific phrases a user would say ("SSL certificates", "high response time", "tests not starting", "Chrome Extension export", "New Relic") with good coverage, but lacks synonyms/file extensions that would push it to the comprehensive top anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear BlazeMeter-specific niche with distinct triggers (Radar Agent, Taurus, BlazeMeter-specific features), but the trailing catch-all "or any other troubleshooting tasks" broadens scope and raises minor overlap risk with generic support skills.

4 / 5

Total

17

/

20

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: 5 missing, 5 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.