Outscraper

v1.0.2

Outscraper integration. Manage Organizations. Use when the user wants to interact with Outscraper data.

0· 101·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Outscraper integration) matches the SKILL.md: it instructs use of the Membrane CLI to connect to Outscraper and run scraping/extraction actions. No unrelated services, credentials, or binaries are requested.
Instruction Scope
Instructions focus on installing and using the Membrane CLI, logging in, creating a connector, and calling Outscraper-related actions. They do not ask the agent to read unrelated files, environment variables, or transmit data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no install spec in registry). It recommends installing @membranehq/cli globally via npm, which is expected for a CLI-driven integration but does install code system-wide and requires network/npm access.
Credentials
The skill declares no required env vars or credentials (Membrane handles auth). Requiring a Membrane account is reasonable for a connector workflow; there are no disproportionate or unrelated secret requests.
Persistence & Privilege
The skill does not request always: true or other elevated persistence. It is user-invocable and allows normal autonomous invocation (platform default). It does not modify other skills or system-wide configs in the provided instructions.
Assessment
This skill uses the Membrane CLI to connect to Outscraper and relies on your Membrane account for authentication. Before installing/using: (1) Confirm you trust getmembrane.com/@membranehq and the @membranehq/cli npm package, since installing a global npm package runs code on your machine. (2) Be aware auth is done through your browser (or headless flow) so connector tokens/credentials are managed by Membrane — review Membrane's privacy/security docs. (3) Do not provide unrelated secrets to the skill; run initial installs/commands in an environment you control (or a container) if you want to limit risk. Overall the skill is coherent with its stated purpose, but validate the third-party Membrane tooling before granting access.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d30p6ngt5kbr177a6aq6eps843kav

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments