Scrapingbee
v1.0.2ScrapingBee integration. Manage Projects, Users. Use when the user wants to interact with ScrapingBee data.
⭐ 0· 115·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 (ScrapingBee integration) matches the SKILL.md: all actions are routed through the Membrane CLI to manage ScrapingBee connections, actions, and proxy requests. No unrelated credentials or system access are requested.
Instruction Scope
The instructions tell the user/agent to install and run the Membrane CLI, perform an interactive login (browser-based or headless flow), list actions, run actions, and proxy arbitrary API paths via Membrane. This is expected for a proxy-based integration, but it means the agent will run shell commands and can send arbitrary requests through the Membrane connection (which is inherent to the integration).
Install Mechanism
There is no automated install spec in the registry; the SKILL.md suggests installing @membranehq/cli with `npm install -g`. This is a common package install pattern but it writes a global binary and fetches code from the npm registry — the user should ensure they trust the package and have permission to install global npm packages. No opaque download URLs or extract steps are present.
Credentials
The skill declares no environment variables or credentials and explicitly directs the user to let Membrane manage credentials server-side (do not ask for API keys). Requested access is proportional to the stated goal of interacting with ScrapingBee.
Persistence & Privilege
The skill is not force-installed (always: false) and doesn't request elevated platform privileges or modify other skills. Normal autonomous invocation is allowed by default; nothing in the skill attempts permanent presence or cross-skill configuration changes.
Assessment
This skill is instruction-only and relies on the Membrane CLI to act as a proxy to ScrapingBee. Before using it: (1) verify you trust the Membrane project and the npm package @membranehq/cli (installing it globally will write a binary to your system); (2) be aware the CLI login opens a browser-based auth flow and Membrane will hold credentials and perform requests on your behalf — only create connections you trust; (3) the skill can instruct the agent to send arbitrary API requests via the connection, so limit use to trusted connectors and review any commands before running them; (4) if you need stricter isolation, run the CLI in a controlled environment (container or VM) or avoid installing global npm packages. Otherwise, the skill's instructions and requirements are coherent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk973gecr4t1sd34bhnpwc442rs843w4t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.