Lambdatest
v1.0.0Lambdatest integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lambdatest data.
⭐ 0· 52·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
high confidencePurpose & Capability
The name/description (Lambdatest integration) align with the instructions: all runtime guidance is about using the Membrane CLI to discover connections, run actions, and proxy requests to the LambdaTest API. There are no unrelated credentials, binaries, or paths requested.
Instruction Scope
SKILL.md stays on-topic: it instructs the agent to install/use the Membrane CLI, authenticate via Membrane, list/connect to a LambdaTest connector, run actions, or proxy API requests. It does not instruct reading local secrets or unrelated system files.
Install Mechanism
No bundled install spec in the registry (skill is instruction-only), but the README asks users to install an npm package (@membranehq/cli) globally or use npx. Installing an npm CLI is common but is a moderate-risk action because it runs third-party code on the host; consider preferring npx or reviewing the package source before global install.
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane to handle auth, which is consistent with the documentation in SKILL.md. No surprising credential requests are present.
Persistence & Privilege
The skill does not request always-on presence and contains no instructions to modify other skills or system-wide config. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill appears to be what it claims: it delegates LambdaTest access to the Membrane service and provides CLI instructions. Before installing or using it: (1) verify you trust Membrane (review getmembrane.com, the GitHub repo, and the @membranehq/cli package source), (2) prefer running the CLI via npx if you want to avoid a global install, (3) understand that API calls and credentials will be proxied through Membrane (read their privacy/security docs), and (4) test in a limited environment or sandbox account first. If you require stricter control, contact Membrane/LambdaTest support or use direct LambdaTest API access instead of a third‑party proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk978d2xq2sn4dp15a8rdb9z41h84dxrs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.