CtrlK
BlogDocsLog inGet started
Tessl Logo

blazemeter-service-virtualization

Comprehensive guide for BlazeMeter Service Virtualization, including virtual services, transactions, templates, and management. Use when working with Service Virtualization for (1) Creating virtual services and transactions, (2) Managing services (clone, export/import, rename/delete), (3) Using templates and environment variables, (4) Adding processing actions to transactions, (5) Using test data with virtual services, (6) Understanding transactional analytics, or any other Service Virtualization tasks.

60

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

The SKILL.md body is a well-structured, navigable overview with correctly signaled, verified one-level-deep reference files — strong progressive disclosure. Its weaknesses are repetitive capability restatements and a lack of executable, validated steps for the core service-management tasks, which are deferred entirely to references.

Suggestions

Consolidate the redundant capability lists in 'Quick Start', 'When to Use MCP Tools', and 'When to Use Each Reference' into a single source to remove repetition.

Add a concise, concrete worked example (e.g., a minimal sequence to create and start a virtual service from a transaction) so the highest-value task is actionable without immediately opening a reference.

For destructive/batch operations (rename/delete, export/import, clone), include an explicit verification step such as confirming the service state before and after the action.

DimensionReasoningScore

Conciseness

The body is largely lean and avoids explaining concepts Claude already knows, but the 'Quick Start', 'When to Use MCP Tools', and 'When to Use Each Reference' sections restate the same capability lists already covered by the description and reference file annotations, adding repetition rather than new information.

2 / 3

Actionability

It gives some concrete guidance — named MCP tools with actions and required args and a numbered example workflow — but the core Service Virtualization work itself is only pointed at via reference links rather than given executable steps, so the most important task lacks copy-paste-ready instruction.

2 / 3

Workflow Clarity

The MCP example workflow is a clear numbered sequence, but operations like clone/export-import and service management involve batch or potentially destructive changes yet have no validation or verification checkpoints described in the body.

2 / 3

Progressive Disclosure

The body is a well-organized overview that links to real one-level-deep reference files (introduction.md, transactions.md, virtual-services.md, management.md, analytics.md, all verified present), each annotated with its scope and grouped under clear headings, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

9

/

12

Passed

Description

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.

The description is comprehensive, specific, and supplies an explicit 'Use when' trigger with enumerated scenarios, covering both what the skill does and when to use it. Its main weakness is reliance on product-specific jargon rather than the natural, varied phrasings a user might actually say.

Suggestions

Add natural-language trigger variations users would actually say (e.g., 'mock services', 'simulate APIs', 'stub dependencies for testing') alongside the product terminology.

Trim the enumerated (1)-(6) list slightly, since the trailing 'or any other Service Virtualization tasks' already provides a catch-all, reducing length without losing triggers.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions and domains: 'Creating virtual services and transactions', 'Managing services (clone, export/import, rename/delete)', 'Using templates and environment variables', 'Adding processing actions to transactions', 'Using test data', and 'Understanding transactional analytics', which matches the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers 'what' (the enumerated Service Virtualization capabilities) and 'when' with an explicit 'Use when working with Service Virtualization for (1)...(6)...or any other Service Virtualization tasks' trigger clause, satisfying the highest anchor.

3 / 3

Trigger Term Quality

It surfaces domain-relevant terms like 'virtual services', 'transactions', 'templates', 'processing actions', and 'test data', but these are product-jargon terms a user is less likely to spontaneously utter than natural variations, and common phrasings a user might say ('simulate APIs', 'mock services', 'stub dependencies') are missing.

2 / 3

Distinctiveness Conflict Risk

The tightly scoped 'BlazeMeter Service Virtualization' niche with specific trigger scenarios around virtual services, transactions, and processing actions makes it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.