Saucelabs

v1.0.2

SauceLabs integration. Manage Users, Organizations, Files, Notes, Activities. Use when the user wants to interact with SauceLabs data.

0· 141·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md explains using Membrane as a proxy/connector to interact with Sauce Labs. Requiring network access and a Membrane account fits the stated purpose; no unrelated services, binaries, or env vars are requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, creating a connection, listing/running actions, and proxying requests. The document does not instruct reading arbitrary local files or exfiltrating unrelated data.
Install Mechanism
There is no platform install spec (this is instruction-only), but the SKILL.md recommends installing @membranehq/cli via npm -g or using npx. Installing a global npm package is a normal user step but carries standard risks (npm packages run code during install); verify the package source before installation.
Credentials
The skill requests no local env vars or credentials and explicitly instructs to let Membrane handle auth. This is proportionate, but it means Sauce Labs credentials are stored/managed by Membrane (a third party), which users should consider.
Persistence & Privilege
The skill does not request permanent/always-on privileges, does not modify other skills, and requires no config paths. Autonomous invocation is allowed but is the platform default and not, by itself, a problem.
Assessment
This skill is coherent: it relies on the Membrane service/CLI to talk to Sauce Labs rather than handling credentials locally. Before installing or using it, verify the @membranehq/cli npm package and the Membrane service (official site, package integrity). Be aware that your Sauce Labs credentials will be managed by Membrane — consider using a least-privilege account or reviewing Membrane's privacy/security documentation. Installing the CLI globally (npm -g) requires appropriate permissions and installs third-party code on your machine, so confirm you trust the source. If you prefer not to share credentials with a third party, do not create the Membrane connection.

Like a lobster shell, security has layers — review code before you run it.

latestvk977pgx32d80w2jmm4axwvv77h842ktx

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments