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.
57
65%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./resources/skills/blazemeter-functional-testing/SKILL.mdQuality
Discovery
85%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 around BlazeMeter Functional Testing with specific capabilities enumerated and explicit trigger conditions. The numbered use-case list and deprecation note add valuable disambiguation. The main weakness is that trigger terms lean toward product documentation terminology rather than natural user language, which could slightly reduce matching for users who phrase requests more casually.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: creating GUI Functional Tests (with specific formats: YAML, Java IDE, Python IDE), managing tests (duplicate, delete, move, rename), using test data, working with Action Library, debugging, and understanding browser support. These are detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter Functional Testing covering GUI tests, API tests, Action Library, debugging) and 'when' (explicit 'Use when working with Functional Testing for...' clause with six numbered trigger scenarios plus a catch-all). Also includes a helpful deprecation note about API Functional Tests. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'BlazeMeter', 'Functional Testing', 'GUI Functional Tests', 'API Tests', 'Action Library', 'debugging', 'YAML', 'Java IDE', 'Python IDE'. However, it's somewhat jargon-heavy and may miss natural user phrasings like 'functional test script', 'test automation', 'record and playback', or 'BlazeMeter test setup'. The terms are more product-documentation-oriented than user-query-oriented. | 2 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to BlazeMeter Functional Testing, which is a distinct product domain. The mention of specific sub-features (Action Library, GUI Functional Tests, YAML/Java/Python IDEs) and the deprecation note about API Monitoring clearly delineate this skill's scope from general testing or API monitoring skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves primarily as a navigation hub pointing to reference files, which it does reasonably well. However, it lacks concrete, executable examples and meaningful workflow guidance — the MCP tools section describes capabilities without showing actual usage with real parameters. The content could be significantly tightened by removing redundant sections (Quick Start vs Reference Files vs When to Use Each Reference all overlap).
Suggestions
Add a concrete, executable MCP tool example with actual parameters and expected output (e.g., `blazemeter_tests` with action `list` showing a real project_id and sample JSON response).
Remove the 'When to Use Each Reference' section as it duplicates information already conveyed in the Reference Files section headers and descriptions.
Add validation/verification steps to the Example Workflow, such as checking execution status codes or verifying test completion before reviewing results.
Collapse the Quick Start into the Reference Files section or make it genuinely actionable with specific first steps rather than a topic list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary repetition (e.g., 'When to Use Each Reference' largely duplicates the Reference Files section headings) and includes some filler phrases like 'Comprehensive guide for creating and managing Functional Tests in BlazeMeter.' However, it's not excessively verbose and mostly stays focused. | 2 / 3 |
Actionability | The MCP tools section provides specific tool names, actions, and required arguments, which is somewhat concrete. However, there are no executable code examples, no copy-paste ready commands, and the 'Example Workflow' is just a numbered list of descriptions rather than actual executable steps with concrete parameters or expected outputs. | 2 / 3 |
Workflow Clarity | The 'Example Workflow' section lists steps but lacks any validation checkpoints, error handling, or feedback loops. The Quick Start is just a topic list, not a workflow. There's no guidance on what to do when things go wrong, and the steps are vague ('Review execution results for functional test outcomes'). | 1 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to specific topic files (gui-tests.md, api-tests.md, action-library.md, debugging.md, browsers.md). Each reference is clearly labeled with its contents, and navigation is straightforward. | 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.