Blazemeter
v1.0.2Blazemeter integration. Manage data, records, and automate workflows. Use when the user wants to interact with Blazemeter data.
⭐ 0· 93·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (Blazemeter integration) match the instructions: the SKILL.md shows how to discover connectors/actions and proxy Blazemeter API calls via the Membrane CLI. Requiring a Membrane account and installing @membranehq/cli is coherent with that design. Note: the skill delegates all networking/auth to Membrane (homepage points to getmembrane.com) rather than calling Blazemeter APIs directly — this is a design choice but should be expected by users.
Instruction Scope
Instructions are focused on using the Membrane CLI (login, connect, action list/run, request proxy). They require network access and interactive browser auth or headless token completion. Important privacy/flow note: requests and request payloads will be proxied through Membrane, and the CLI will persist auth tokens/config locally; the SKILL.md does not instruct reading unrelated files or environment variables.
Install Mechanism
There is no platform install spec in the registry metadata, but the SKILL.md instructs installing @membranehq/cli globally via npm (npm install -g @membranehq/cli). Installing a global npm package is a normal, moderate-risk action (it runs code obtained from the npm registry). Users should review the package and trust the publisher before installing.
Credentials
The skill declares no required env vars or credentials in the registry metadata and the instructions likewise do not request unrelated secrets. Authentication is handled interactively via Membrane; therefore the absence of direct Blazemeter API keys is expected. Users should be aware that Membrane will hold or proxy credentials/tokens as part of its flow.
Persistence & Privilege
The skill does not set always:true and is user-invocable only. The only persistence implied is that the Membrane CLI (if installed) will store auth/config locally — that is normal for a CLI tool and within scope for this integration. There is no instruction to modify other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: integrate with Blazemeter via the Membrane platform. Before installing or using it, consider: (1) you will install a third-party npm CLI (@membranehq/cli) which executes code on your machine — review the package and publisher; (2) network requests and authentication flows are proxied through Membrane, so request payloads, test data, and tokens will pass through/be stored by that service — review Membrane's privacy/security docs and trust model; (3) use least-privilege accounts or ephemeral credentials when possible and avoid sending secrets in free-text fields. If you need stronger isolation, run the CLI in a sandboxed environment or review the Membrane CLI source before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk973gsrfemnet50dcrqj03n2ex843c7z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.