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.

65

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-structured index-style skill that uses progressive disclosure effectively, with concrete MCP tool guidance. Its weakness is redundancy between sections and abstract Quick Start steps that describe troubleshooting rather than giving concrete, checkpointed diagnostic actions.

Suggestions

Remove the redundant 'When to Use Each Reference' section (or merge it into 'Reference Files') and delete filler like 'Effective troubleshooting requires systematic diagnosis...' to tighten the body.

Make the Quick Start steps concrete and actionable, e.g. name the specific diagnostic checks to run per issue type instead of 'Apply solutions: Follow diagnostic steps and solutions'.

Add an explicit validation/confirmation checkpoint in the troubleshooting workflow (e.g. 'Confirm the symptom matches a reference case before applying a fix; if the fix fails, escalate to support') to lift workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient but padded in places: the Overview restates the frontmatter and adds filler ("Effective troubleshooting requires systematic diagnosis..."), and "When to Use Each Reference" largely duplicates the "Reference Files" categorization. Not a 3 because several tokens do not earn their place.

2 / 3

Actionability

The MCP tools section is concrete (tool names, actions, required args, return values), but the central Quick Start is abstract ("Apply solutions: Follow diagnostic steps and solutions") and describes rather than instructs. Not a 1 because real executable detail exists for MCP usage.

2 / 3

Workflow Clarity

A sequence is present (identify → check reference → apply → contact support) and the MCP example workflow is clearly ordered, but there are no validation checkpoints between diagnosis and applying fixes. Not below 2 because steps are explicitly listed; not 3 because checkpoints are implicit.

2 / 3

Progressive Disclosure

The body is a concise overview index pointing to five well-signaled, one-level-deep reference files, each annotated with its topics; all referenced files exist and navigation is easy. Matches the clear-overview-with-one-level-references anchor.

3 / 3

Total

9

/

12

Passed

Description

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.

A strong, third-person description that names a concrete domain and enumerates specific issue types with an explicit, well-structured 'Use when' trigger clause. It is comprehensive without devolving into fluff and is unlikely to be selected for the wrong skill.

DimensionReasoningScore

Specificity

Lists multiple concrete issue categories with specific examples ("Radar Agent auth, SSL certificates", "high response time, 500 errors, partial load, tests not starting"), matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ("Comprehensive troubleshooting guide for BlazeMeter, covering...") and when ("Use when troubleshooting for (1)...(6), or any other troubleshooting tasks"), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered ("troubleshooting", "BlazeMeter", "high response time", "500 errors", "tests not starting", "support requests and tickets"), going beyond jargon to common phrasings.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to BlazeMeter with product-specific triggers (Radar Agent, Taurus, New Relic reporting, Apache Log4j2), making conflict with other skills unlikely; not below because the niche is clearly distinct.

3 / 3

Total

12

/

12

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.