Zenscrape
v1.0.2Zenscrape integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zenscrape data.
⭐ 0· 80·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 skill description (Zenscrape integration) aligns with its instructions: it delegates all API/auth work to the Membrane platform and shows commands to discover/connect/run actions against a Zenscrape connector. Requiring the Membrane CLI is coherent for this purpose.
Instruction Scope
SKILL.md restricts runtime actions to installing/using the Membrane CLI, doing browser-based login flows, listing/connecting actions, and proxying API requests through Membrane. It does not instruct reading arbitrary local files, requesting unrelated environment variables, or posting data to unknown endpoints beyond Membrane.
Install Mechanism
There is no automatic install spec in the skill bundle (instruction-only). The instructions recommend a global npm install of @membranehq/cli (a scoped package on npm). This is a common, traceable install method but does write a CLI binary to disk and runs code from the npm registry — a moderate but expected risk for a CLI-based integration.
Credentials
The skill declares no required env vars or credentials and explicitly advises using Membrane to manage secrets. That is proportionate. Note: using the Membrane proxy means data and auth tokens are handled by Membrane's service (getmembrane.com), so users should be comfortable with that data flow.
Persistence & Privilege
The skill does not request always:true, does not alter other skills or system-wide configs, and is user-invocable only. Autonomous invocation is allowed by platform default but not combined with other concerning privileges here.
Assessment
This skill is an instructions-only wrapper that expects you to install and use the @membranehq/cli to manage a Zenscrape connector. Before proceeding: (1) confirm you trust Membrane/getmembrane.com because the CLI and proxy will route requests and credentials through their service; (2) review the @membranehq/cli package and its GitHub repo if you want to audit what the CLI does locally (global npm installs add binaries to your system); (3) be aware that authentication is done in-browser and tokens will be managed by Membrane, so verify the connector permissions you grant (access to Zenscrape data); (4) because the skill is instruction-only, it won’t auto-install anything, but running the recommended commands will install/run external code — proceed only if you accept that tradeoff.Like a lobster shell, security has layers — review code before you run it.
latestvk979qg4jpt8edwb2q6eayx0m0n842xjm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.