Scrapin Io
v1.0.0Scrapin.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scrapin.io data.
⭐ 0· 95·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 and description describe a Scrapin.io integration and all runtime steps use the Membrane CLI to connect to Scrapin.io and run proxy/actions. There are no unrelated requested credentials, binaries, or config paths.
Instruction Scope
SKILL.md contains only guidance to install the Membrane CLI, log in (browser-based auth), create/connect to a Scrapin.io connector, list and run actions, or proxy raw requests. It does not instruct reading unrelated files, exfiltrating local secrets, or contacting endpoints outside Membrane/Scrapin flows.
Install Mechanism
This is an instruction-only skill (no install spec), but the documentation tells the user to install @membranehq/cli globally via npm (-g). Installing a global npm package is a normal step for CLI usage, but it is an outward install action the user must perform and should verify (package name, publisher, and registry) before installing.
Credentials
The skill declares no required env vars or credentials. Authentication is performed via Membrane's browser-based login/connection flow; no local API keys are requested by the skill.
Persistence & Privilege
The skill is not always-enabled and does not request system-level persistence. Autonomous invocation is allowed (platform default) but there are no additional elevated privileges requested.
Assessment
This skill is coherent: it uses the Membrane CLI to manage a Scrapin.io connection and run actions, so the main things to consider before installing/using it are:
- Trust and provenance: The SKILL.md recommends installing @membranehq/cli from npm. Verify the package name, publisher, and npm registry listing (and consider installing without -g or in a sandbox) to avoid supply-chain risk.
- Account and data visibility: Membrane handles auth and proxies requests — that means Membrane (the service) will see requests and responses for your Scrapin.io usage. Only proceed if you trust Membrane with that data and with any connector scopes you authorize in the browser flow.
- Browser-based auth: The flow opens a browser to authenticate and create the connection. In headless contexts you’ll copy a URL and complete a code; ensure you only paste/enter codes on trusted pages.
- Least privilege: When creating the connector, review the scopes/permissions requested so you give only the access you intend.
No scan findings were present (the skill is instruction-only), and the content does not request unrelated secrets or system access. If you need extra assurance, verify the Membrane CLI repo and the Scrapin.io connector manifest before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk977t2gvxcnnz886x44j783r3x84h2g8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
