CtrlK
BlogDocsLog inGet started
Tessl Logo

blazemeter-functional-testing

Comprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3) Using test data in Functional Tests, (4) Working with Action Library, (5) Debugging Functional Tests, (6) Understanding browser support, or any other Functional Testing tasks. Note - API Functional Tests are deprecated in favor of API Monitoring.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A well-structured, concise skill body that points cleanly to one-level-deep reference files and gives concrete MCP tool guidance. Its main weakness is the absence of explicit validation/error-handling checkpoints in the workflow.

Suggestions

Add an explicit validation or error-handling step in the Example Workflow (e.g., check execution status, inspect failures) rather than just 'review execution results'.

Trim the overlap between the Overview and Quick Start sections, which restate the same five categories.

Include one concrete code snippet (e.g., a sample blazemeter_tests read call with arguments) to make the MCP guidance fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient, using brief bullets and short reference descriptions without padding; minor instances of restatement (e.g., the Overview restating the Quick Start categories) could be trimmed.

4 / 5

Actionability

Provides concrete, executable MCP tool guidance with named tools (blazemeter_tests, blazemeter_execution), specific actions (read, list), required args, and a worked example workflow, with only minor gaps in concrete code.

4 / 5

Workflow Clarity

The Example Workflow gives a clear numbered sequence (list -> read -> read execution -> review results) with most steps concrete; it lacks explicit validation checkpoints, but the operations are read-only and non-destructive, so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Clear overview in SKILL.md with well-signaled, one-level-deep references to real files (gui-tests.md, api-tests.md, action-library.md, debugging.md, browsers.md), each annotated with its contents and a 'When to Use Each Reference' section for easy navigation.

5 / 5

Total

17

/

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, comprehensive description that clearly states capabilities and provides explicit, numbered trigger guidance. It is slightly long and could be trimmed, and risks minor overlap with adjacent BlazeMeter skills.

DimensionReasoningScore

Specificity

Names the domain and lists several specific capabilities (GUI Functional Tests, API Tests, Action Library, debugging) with concrete creation methods (YAML, Java IDE, Python IDE) and management actions (duplicate, delete, move, rename), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both 'what' (Comprehensive guide for BlazeMeter Functional Testing, including GUI/API/Action Library/debugging) and 'when' with a detailed 'Use when working with Functional Testing for (1)... (6)...' clause listing concrete triggers.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say ('Creating GUI Functional Tests', 'Managing Functional Tests', 'test data', 'Action Library', 'Debugging Functional Tests', 'browser support'), though it lacks common synonyms and file extensions for the functional-testing domain.

4 / 5

Distinctiveness Conflict Risk

Scoped clearly to BlazeMeter Functional Testing with distinct triggers, but the broad umbrella of 'Functional Testing tasks' creates minor overlap risk with general testing or API Monitoring 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.