Name: blazemeter-usage-billing
Rating: 61.6 (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

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/blazemeter-usage-billing/SKILL.md

Quality

Content

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

The body is well-structured for progressive disclosure — a lean overview pointing to one real reference file — but the substantive guidance is thin: the central credit-calculation task has no inline example or workflow, the MCP workflow lacks validation, and several sections restate the description. It reads more as a table of contents than actionable instruction.

Suggestions

Add a concise inline credit-calculation example (e.g., a VUH formula with a worked number) so the main task is actionable without forcing a jump to the reference.

Tighten or remove redundant restatements of the description ('Guide for understanding...', 'Usage & Billing covers...') and merge the duplicate 'When to Use' trigger lists into one.

Add a validation/verification checkpoint to the billing-info workflow (e.g., confirm the returned billing_usage field is present before reporting).

Dimension	Reasoning	Score
Conciseness	The body restates the description verbatim ('Guide for understanding BlazeMeter usage and billing', 'Usage & Billing covers credit types, charging models...') and includes redundant 'When to Use' sections, so it is mostly efficient but carries padding that could be trimmed, matching the 'mostly efficient, some unnecessary explanation' anchor.	3 / 5
Actionability	It gives concrete, executable MCP guidance (blazemeter_workspaces action read, workspace_id integer, 3-step workflow) but the core credit-calculation task — the skill's main purpose — is fully deferred to the reference with no inline example or formula, leaving key details missing and matching the 'some concrete guidance but incomplete' anchor.	3 / 5
Workflow Clarity	A clear 3-step sequence exists for retrieving billing info but has no validation checkpoint, and the primary credit-calculation task has no sequenced workflow at all; this matches the 'steps listed but validation gaps, checkpoints missing or implicit' anchor.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with a single clearly-signaled, one-level-deep reference to a verified real file ([credits.md](skill-blazemeter-usage-billing://references/credits.md)), with content appropriately split and easy to navigate, matching the clear-overview anchor.	5 / 5
	Total	14 / 20 Passed

Description

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

The description is strong: it states concrete capabilities and provides explicit, enumerated 'Use when' triggers tied to a well-defined BlazeMeter niche. The only weakness is the generic closing clause and a few missing natural synonyms, which keep specificity and trigger_term_quality just below maximum.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete capabilities — 'Understanding BlazeMeter credit types (VU, VUH, Tests)' and 'Calculating credit consumption for different test types' — though the trailing 'any other usage and billing tasks' is generic filler, leaving minor gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both 'what' (guide for usage & billing including credit types and charging) and 'when' with concrete enumerated triggers ('Use when working with usage and billing for (1)... (2)...'), matching the anchor that requires clear what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('credit types', 'calculating credit consumption', 'test types', 'usage and billing') but misses common synonyms/variations like 'cost estimate', 'VUH cost', or 'BlazeMeter billing', matching the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	'BlazeMeter Usage & Billing' is a clearly defined niche with distinct, domain-specific triggers (VU, VUH, credit consumption) that are unlikely to fire for unrelated skills, matching the clear-niche anchor.	5 / 5
	Total	18 / 20 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
Path: resources/skills/blazemeter-usage-billing/SKILL.md
Commit: 95bce72

Reviewed: 5 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.