blazemeter-integrations
Comprehensive guide for BlazeMeter Integrations, including APM tools, CI/CD pipelines, and development tools. Use when working with integrations for (1) Integrating APM tools (AppDynamics, Datadog, New Relic, CloudWatch, DX APM, Dynatrace, Delphix), (2) Integrating CI/CD tools (Jenkins, GitHub Actions, GitLab CI/CD, Azure DevOps, AWS CodePipeline, Bamboo, TeamCity, CircleCI, Codeship), (3) Using development tools (Visual Studio Code Plugin, MCP Server), or any other integration tasks.
76
63%
Does it follow best practices?
Impact
100%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./resources/skills/blazemeter-integrations/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 clearly defines its scope around BlazeMeter integrations, provides comprehensive trigger terms through exhaustive tool listings, and explicitly states when it should be used. The structured enumeration of three integration categories with specific tool names makes it both highly discoverable and clearly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions organized into three clear categories: APM tool integrations, CI/CD pipeline integrations, and development tool integrations, each with named tools. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for BlazeMeter integrations across APM, CI/CD, and dev tools) and 'when' (explicit 'Use when working with integrations for...' clause with numbered trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say, including specific tool names (Jenkins, GitHub Actions, Datadog, New Relic, etc.), category terms (APM, CI/CD), and general terms (integrations, development tools, Visual Studio Code Plugin, MCP Server). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific BlazeMeter context combined with exhaustive lists of named integration tools. The niche is clear and unlikely to conflict with other skills unless there are separate per-tool BlazeMeter skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structural organization with clear progressive disclosure to reference files, but the body content itself is largely filler. The MCP tools listing is verbose without being actionable—it catalogs tools without showing concrete invocation syntax or parameters. The skill would benefit significantly from replacing abstract descriptions with executable examples and trimming redundant explanatory text.
Suggestions
Replace the abstract 'Example Workflows' with concrete, executable tool invocations showing actual parameters, expected inputs, and expected outputs (e.g., actual MCP tool call syntax with sample parameters).
Remove or drastically condense the MCP Tools listing—either link to a reference file for the full API catalog or show only the 2-3 most commonly used tools with concrete usage examples.
Eliminate redundant sections like 'When to Use Each Reference' and 'When to Use MCP Tools' that restate what's already obvious from context and headings.
Add validation checkpoints to the CI/CD workflow (e.g., verify test exists and is configured before starting execution, check execution status before reading summary, handle failure cases).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows or can infer. The MCP Tools section is an extensive API listing that largely restates tool names and actions without adding actionable value. The 'When to Use MCP Tools' section lists obvious use cases (e.g., 'Automation: Automate integration workflows'). The 'When to Use Each Reference' section at the bottom repeats what's already clear from the reference file names and descriptions. | 1 / 3 |
Actionability | The skill provides no concrete, executable code, commands, or configuration examples. The 'Example Workflows' are abstract step descriptions (e.g., 'Use blazemeter_tests with action list to find tests') without actual tool invocation syntax, parameters, or expected outputs. There are no copy-paste ready examples for any of the APM, CI/CD, or development tool integrations. | 1 / 3 |
Workflow Clarity | The example workflows provide a basic sequence of steps, but they lack validation checkpoints, error handling, and feedback loops. For CI/CD integration workflows that involve test execution (a potentially destructive/costly operation), there's no mention of verifying test configuration before starting, handling execution failures, or timeout considerations. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear one-level-deep references to apm.md, cicd.md, and development-tools.md. The reference files are clearly signaled with descriptive content summaries, and navigation is straightforward. The content is appropriately split between overview and detailed reference files. | 3 / 3 |
Total | 7 / 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
6395eba
- 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.