Webscraperio
v1.0.2WebScraper.IO integration. Manage data, records, and automate workflows. Use when the user wants to interact with WebScraper.IO data.
⭐ 0· 75·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description say it's a WebScraper.IO integration and the SKILL.md exclusively instructs using the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests — which fits the stated purpose.
Instruction Scope
Runtime instructions are focused: install and use @membranehq/cli, run membrane login/connect/action/request commands, and use the proxy for API calls. The instructions do not ask to read unrelated files, export unrelated environment variables, or exfiltrate data. Headless auth flow and browser-based login are documented and reasonable.
Install Mechanism
The skill is instruction-only (no install spec in the registry), but SKILL.md recommends installing the Membrane CLI via `npm install -g @membranehq/cli`. This is a normal approach but means the user will run a global npm install outside the registry-managed install flow — recommend verifying the npm package and publisher before installing.
Credentials
No environment variables, secrets, or config paths are requested by the skill. The SKILL.md explicitly recommends letting Membrane handle credentials server-side instead of asking for API keys locally, which is proportionate to the integration.
Persistence & Privilege
Skill metadata does not request always:true and is user-invocable; it does not request system-wide config changes or persistent presence beyond normal use. Autonomous invocation is allowed by default but not combined with other red flags.
Assessment
This skill appears coherent and limited to using the Membrane CLI to interact with WebScraper.IO. Before installing/using it: (1) verify the @membranehq/cli package on npm and confirm the publisher and package integrity; (2) review Membrane's privacy/security docs because the CLI and Membrane service act as an authentication proxy and will have access to your WebScraper.IO connection; (3) prefer running the CLI in an environment you control (or isolated container) if you are cautious about installing global npm packages; and (4) never paste raw API keys or unrelated secrets into chat — the skill's instructions explicitly advise not to. If you want extra assurance, confirm the referenced repository and homepage links resolve to the official project before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk977epej8mpjn310jh0zmv9mvh843byh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.