Browserstack
v1.0.2BrowserStack integration. Manage data, records, and automate workflows. Use when the user wants to interact with BrowserStack data.
⭐ 0· 112·1 current·1 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (BrowserStack integration) match the instructions: all actions are performed via the Membrane CLI which proxies calls to BrowserStack. Nothing in the SKILL.md asks for unrelated services or credentials.
Instruction Scope
The SKILL.md instructs the agent/user to install and run the Membrane CLI, create a connection, list and run actions, or proxy API requests through Membrane. It does not instruct reading arbitrary local files, accessing unrelated environment variables, or sending data to unexpected endpoints.
Install Mechanism
No install spec is bundled with the skill (instruction-only). The doc recommends installing @membranehq/cli via npm globally (public registry). npm global installs are standard but carry typical supply-chain and permission considerations (requires elevated privileges on some systems). This is moderate risk but appropriate for the stated workflow.
Credentials
The skill declares no required env vars or credentials and explicitly tells users not to supply BrowserStack API keys locally; it relies on Membrane to handle auth. The requested access is proportional to the task.
Persistence & Privilege
The skill is not always-enabled and does not request permanent or elevated platform-level privileges. It is an instruction-only integration that relies on the Membrane CLI and the user's account for auth.
Assessment
This skill appears coherent and does what it claims: use the Membrane CLI to interact with BrowserStack. Before installing or following the instructions: (1) verify the npm package name (@membranehq/cli) and its publisher on the npm registry and review its repository to ensure it’s official; (2) be aware a global npm install may require elevated permissions and carries normal supply-chain risk; (3) you will need a Membrane account and network access and will authenticate via a browser flow — do not paste BrowserStack API keys into chat or local files unless you understand the implications; (4) if you need higher assurance, ask the skill author for the exact source repo/commit used by the CLI and inspect that code before installation.Like a lobster shell, security has layers — review code before you run it.
latestvk97dz1m4bqtm483926eb5wk221842gjb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.