Browserless
v1.0.1Browserless integration. Manage data, records, and automate workflows. Use when the user wants to interact with Browserless data.
⭐ 0· 68·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 say 'Browserless' and the SKILL.md describes using Membrane to connect to Browserless, run actions, and proxy API calls. Required capabilities (network + Membrane account) match the stated purpose; there are no unrelated credential or filesystem requirements.
Instruction Scope
Instructions are narrowly focused: install the Membrane CLI, login, create or locate a Browserless connection, list/run actions or proxy requests. The doc does not instruct reading unrelated files, grabbing environment secrets, or exfiltrating data to unexpected endpoints.
Install Mechanism
No platform-level install spec is present, but SKILL.md instructs users to run `npm install -g @membranehq/cli`. Installing a globally published npm CLI is a common pattern but carries the usual risk of executing third-party code from the npm registry. The instruction is expected for this skill, but you should verify the package's authenticity (publisher, repo) before installing.
Credentials
The skill requests no environment variables or secret values in the registry. Authentication is delegated to Membrane (browser auth flow and server-side token management), which is proportionate to the goal of accessing Browserless without storing local API keys.
Persistence & Privilege
The skill is not always-on, is user-invocable, and does not request elevated platform privileges or modify other skills. It does not ask to write persistent agent-wide config beyond using the Membrane CLI during setup.
Assessment
This skill is internally consistent with its stated purpose, but before installing or running it: (1) verify the @membranehq/cli npm package (publisher, repository, recent releases) because running `npm install -g` executes third-party code; (2) be prepared for an interactive login flow (or the headless 'login complete' flow) and confirm you are comfortable delegating Browserless auth to Membrane; (3) do not supply Browserless API keys directly unless you understand the implications; and (4) if you need higher assurance, inspect the Membrane CLI source or run it in an isolated environment (container/VM) before granting it access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk978t9aw2ktzyrq8bktcy7agz984arw0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.