CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

85

1.20x
Quality

Does it follow best practices?

Impact

100%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

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 content is well-structured for progressive disclosure, with a lean overview linking to real reference files. It is weaker on conciseness due to repeated restating of the three categories, and on actionability/workflow clarity because in-body guidance relies on tool/action listings rather than executable commands or validation checkpoints.

Suggestions

Collapse the redundant restatements of the APM / CI-CD / Development Tools split: keep the Overview and remove the near-duplicate Quick Start and 'When to Use Each Reference' sections, or merge them into the Reference Files list.

Add at least one concrete, executable example for the core integration tasks (e.g., a sample Jenkins pipeline snippet or a curl/MCP call) instead of only deferring to reference files.

Add a validation/verification checkpoint to the example workflows, such as confirming an execution reached a terminal state before reading its summary.

DimensionReasoningScore

Conciseness

The body is mostly list-based and avoids explaining concepts Claude knows, but the three-category split (APM / CI-CD / Development Tools) is restated four times across the intro, Overview, Quick Start, and 'When to Use Each Reference' sections, which is padding that could be tightened.

2 / 3

Actionability

The MCP tools section gives concrete tool/action pairs and sequenced example workflows, but the core APM and CI/CD integration guidance is deferred to reference files with no in-body commands or code, leaving the overview itself with incomplete executable detail.

2 / 3

Workflow Clarity

Example workflows are presented as clear numbered sequences, but there are no validation or verification checkpoints (e.g., confirming an execution started or a summary is complete), which leaves the sequence present but checkpoints implicit.

2 / 3

Progressive Disclosure

The body is a clear overview pointing to three real, one-level-deep reference files (apm.md, cicd.md, development-tools.md), each link accompanied by a description of its contents, giving easy navigation and an appropriate content split.

3 / 3

Total

9

/

12

Passed

Description

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.

The description is well-constructed: it states concrete capabilities, enumerates natural trigger terms, includes an explicit 'Use when...' clause, and occupies a clear niche with low conflict risk. Voice is third person, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Integrating APM tools', 'Integrating CI/CD tools', 'Using development tools') and enumerates the specific named tools under each, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does ('Comprehensive guide for BlazeMeter Integrations...') and when to use it with a clear 'Use when working with integrations for...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Covers the natural tool names users would say (AppDynamics, Datadog, New Relic, Jenkins, GitHub Actions, GitLab CI/CD, Azure DevOps) plus 'APM tools' and 'CI/CD pipelines', giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Scoped to BlazeMeter integrations with a distinct, named toolset, making it unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

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: 3 missing, 3 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.