Name: blazemeter-usage-billing
Rating: 62.4 (1 reviews)
Author: Blazemeter

blazemeter-usage-billing

Guide for BlazeMeter Usage & Billing, including credit types and charging. Use when working with usage and billing for (1) Understanding BlazeMeter credit types (VU, VUH, Tests), (2) Calculating credit consumption for different test types, or any other usage and billing tasks.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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, simple read-only skill with good progressive disclosure and a concrete MCP tool pointer. It is held back by redundancy across the Overview/Quick Start/When-to-Use sections and by incomplete actionable detail (no example payload, calculations offloaded to the reference).

Suggestions

Collapse the Overview, Quick Start, and 'When to Use This Reference' sections into a single concise block to remove restated content like 'This skill helps you understand how credits are consumed'.

Add a short example showing the `blazemeter_workspaces` action=`read` request and the shape of the billing usage data returned, so the workflow is copy-paste ready.

Either inline a minimal credit-consumption calculation example or explicitly state up front that all calculation specifics live in references/credits.md so the delegation is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the Overview, Quick Start, and 'When to Use' sections restate the same points, and phrases like 'This skill helps you understand how credits are consumed' add conceptual padding Claude does not need.	2 / 3
Actionability	The MCP tool block is concrete (tool name, action `read`, required `workspace_id`, return shape), but there is no example request/response payload and the actual credit-consumption calculations are delegated to credits.md rather than shown, leaving guidance incomplete.	2 / 3
Workflow Clarity	The example workflow lists a clear read sequence (read workspace → extract billing → use for reporting), but the steps are generic and lack any validation/checkpoint detail; acceptable for a read-only task but it sits at the 'steps listed, checkpoints implicit' anchor.	2 / 3
Progressive Disclosure	Clear sectioned overview with a single well-signaled one-level-deep reference to the existing references/credits.md; detailed credit material is appropriately split out, and navigation is easy.	3 / 3
	Total	9 / 12 Passed

Description

90%

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 with explicit trigger guidance and good natural-term coverage. Its only weakness is that the listed capabilities lean toward topics ('Understanding', 'Calculating') rather than sharply concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete credit types ('VU, VUH, Tests') and two tasks, but the actions ('Understanding', 'Calculating') are topical rather than a list of multiple concrete operations, so it falls short of the level-3 anchor.	2 / 3
Completeness	Explicitly states what it does ('Guide for BlazeMeter Usage & Billing, including credit types and charging') and when to use it ('Use when working with usage and billing for (1)... (2)...'), satisfying both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural terms a user would actually say when needing this skill ('BlazeMeter', 'usage and billing', 'credits', 'VUH'), matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (BlazeMeter billing) with distinct, domain-specific triggers unlikely to collide with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: Blazemeter/bzm-mcp
Commit: aecc244

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.