blazemeter-test-data
Comprehensive guide for BlazeMeter Test Data Management, including data entities, parameters, generation, orchestration, and management operations. Use when working with test data for (1) Creating and managing data entities and parameters, (2) Generating synthetic test data with seed lists and functions, (3) Using test data in tests (CSV, Data Entities), (4) Managing test data (backup, import/export, sharing), (5) Using Test Data Orchestration and Profiler, (6) Working with Test Data Pro, or any other Test Data Management tasks.
66
78%
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-test-data/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 follows the recommended pattern closely. It provides specific capabilities, uses natural trigger terms tied to the BlazeMeter TDM domain, includes an explicit 'Use when' clause with enumerated scenarios, and is highly distinctive due to the product-specific terminology. The description is well-structured and comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: creating/managing data entities and parameters, generating synthetic test data with seed lists and functions, using test data in tests (CSV, Data Entities), backup/import/export/sharing, Test Data Orchestration and Profiler, and Test Data Pro. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter Test Data Management with specific capabilities listed) and 'when' (explicit 'Use when working with test data for...' clause with six enumerated trigger scenarios plus a catch-all). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BlazeMeter', 'test data', 'data entities', 'parameters', 'synthetic test data', 'seed lists', 'CSV', 'backup', 'import/export', 'Test Data Orchestration', 'Profiler', 'Test Data Pro'. These cover a wide range of terms a user working with BlazeMeter TDM would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'BlazeMeter' and the focused domain of 'Test Data Management'. The specific features like Test Data Orchestration, Profiler, and Test Data Pro create a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves as a reasonable overview/index for BlazeMeter Test Data Management with good progressive disclosure to reference files. However, it lacks concrete, executable examples and validation steps in its workflows. The content could be tightened by removing redundant sections (e.g., 'When to Use Each Reference' duplicates information already present in the Reference Files section).
Suggestions
Add concrete, executable MCP tool call examples with specific parameter values and expected output snippets instead of abstract descriptions.
Remove the 'When to Use Each Reference' section as it duplicates the descriptions already provided in the 'Reference Files' section.
Add validation/verification steps to the Example Workflow, such as checking that test data entities are properly attached or that execution results contain expected data patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary padding — the 'When to Use Each Reference' section largely duplicates what's already clear from the Reference Files section headings and descriptions. The 'When to Use MCP Tools' subsection also restates obvious use cases. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The MCP tools section provides some concrete guidance with tool names, actions, and required args, but lacks executable examples (no actual API calls, no concrete parameter values, no expected output). The 'Example Workflow' is a sequence of descriptions rather than copy-paste-ready commands or code. | 2 / 3 |
Workflow Clarity | The example workflow provides a numbered sequence but lacks validation checkpoints or error handling. There's no feedback loop for when things go wrong, and the steps are descriptive rather than precise. For a skill involving test data management, verification steps (e.g., confirming data entity attachment, validating generated data) are missing. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to five categorized reference files. Each reference file is clearly signaled with descriptive content summaries, making navigation straightforward. The organization into Core Concepts, Management, Generation, Orchestration, and Pro is logical. | 3 / 3 |
Total | 9 / 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.