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.
74
60%
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 follows the pattern of good examples in the rubric. It clearly defines the scope (BlazeMeter integrations), enumerates specific tools across three well-organized categories, and includes an explicit 'Use when' clause with detailed trigger conditions. The extensive list of specific tool names serves as excellent trigger terms for skill selection.
| 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, with specific tool names enumerated for each category. | 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 and a catch-all for other integration tasks). | 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, integrations), and product names (BlazeMeter, Visual Studio Code). These are terms users would naturally mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific BlazeMeter context and the exhaustive enumeration of supported tools. The combination of BlazeMeter + specific integration tool names creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is largely a table of contents with an inlined API reference, lacking any concrete, executable guidance. It explains what integrations exist and lists MCP tool actions but never shows how to actually use them with real parameters, configuration, or code. The content is verbose relative to its informational value, with multiple sections restating the same categorization (APM/CI-CD/Dev Tools).
Suggestions
Replace the abstract 'Example Workflows' with concrete, executable examples showing actual MCP tool calls with real parameters and expected responses.
Move the MCP Tools API reference listing to a separate reference file and keep only a brief summary with a link in SKILL.md.
Remove redundant sections like 'When to Use Each Reference' and the Quick Start that merely restate the overview categories.
Add at least one complete, copy-paste-ready integration example (e.g., a Jenkins pipeline snippet or GitHub Actions workflow YAML) to make the skill actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with unnecessary information. The MCP Tools section is an extensive API reference listing that Claude doesn't need spelled out in this detail. The 'When to Use MCP Tools' section restates obvious concepts. The 'When to Use Each Reference' section at the bottom repeats what's already clear from the reference file descriptions. The Quick Start section is just a restatement of the overview. | 1 / 3 |
Actionability | There is no concrete, executable code or specific commands anywhere in the skill. The 'Example Workflows' are abstract step descriptions rather than actual executable examples. No configuration snippets, no CLI commands, no API call examples with parameters — everything is vague direction like 'Access APM credential information' and 'Use results to set CI/CD pipeline status.' | 1 / 3 |
Workflow Clarity | The example workflows provide a basic sequence of steps, but they lack validation checkpoints, error handling, and concrete details. Steps like 'Use results to set CI/CD pipeline status' are vague. There are no feedback loops or verification steps for what to do if a test execution fails or returns unexpected results. | 2 / 3 |
Progressive Disclosure | The skill does reference external files (apm.md, cicd.md, development-tools.md) with clear one-level-deep navigation, which is good. However, the MCP Tools section is a large inline API reference that could be in a separate file, and no bundle files were provided to verify the references actually exist and contain useful content. | 2 / 3 |
Total | 6 / 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.