Zenrows

v1.0.2

ZenRows integration. Manage data, records, and automate workflows. Use when the user wants to interact with ZenRows data.

0· 93·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill claims to integrate with ZenRows and its instructions consistently show using Membrane as the integration layer. Required tools and commands (membrane CLI, membrane action/request) align with that purpose.
Instruction Scope
The SKILL.md instructs the agent/user to install and run the Membrane CLI, perform interactive login (opens a browser or uses a headless code flow), discover actions, run actions, and proxy requests to ZenRows. These actions are within scope, but they involve invoking an external CLI and performing authentication flows — the user should expect network activity and browser-based auth.
Install Mechanism
No automated install is embedded in the registry (instruction-only). The SKILL.md recommends installing @membranehq/cli globally via npm, which is a normal approach but carries the usual npm-global install risk (installing and running code from the npm package).
Credentials
The skill declares no environment variables and does not request unrelated credentials. It explicitly advises against asking the user for API keys and instead uses Membrane to manage credentials, which is proportionate to the stated integration goal. Users should be aware that Membrane will hold/mediate credentials server-side.
Persistence & Privilege
The skill does not request always:true, does not modify other skill configurations, and asks the user to run a standard login flow. There is no indication of elevated or persistent privileges beyond installing and running a CLI the user consents to.
Assessment
This skill is coherent but depends on trusting Membrane (@membranehq) as the intermediary: installing the recommended npm package and performing 'membrane login' will give Membrane control of the ZenRows connection and related tokens. Before installing, verify the @membranehq/cli package and its repository (check npmjs, GitHub, and getmembrane.com), and review Membrane's privacy/security docs to understand how they store and proxy credentials. Remember that running a global npm package executes code from that package — only proceed if you trust the publisher. If you prefer not to give a third party access to your ZenRows account, consider integrating with ZenRows directly instead of using Membrane.

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

latestvk97dhwh5cg92nnghgvtfy33q5x8426p1

License

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

Comments