Smartproxy
v1.0.2Smartproxy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Smartproxy data.
⭐ 0· 104·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 (Smartproxy integration) matches the instructions: all operations are performed via the Membrane CLI and Membrane connections to Smartproxy. There are no unrelated required env vars, binaries, or config paths.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, logging in via Membrane, creating connections, running connector actions, and proxying requests through Membrane. It does not instruct the agent to read arbitrary local files or to exfiltrate data to endpoints outside Membrane/Smartproxy.
Install Mechanism
There is no automated install spec in the manifest (instruction-only), but the README instructs users to run `npm install -g @membranehq/cli`. Installing a global npm package is a user action and is reasonable for this integration, but it carries the usual moderate risk of running code from the public npm registry—verify the package/publisher before installing.
Credentials
The skill requests no environment variables or credentials in the manifest. The instructions explicitly delegate auth to Membrane (login flow) and advise against asking users for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
Skill is instruction-only, has no install-time persistence, and does not set always:true. Autonomous invocation is allowed (platform default), but there is no evidence this skill requires elevated or persistent system privileges.
Assessment
This skill appears to be what it claims: a Smartproxy integration that relies on the Membrane CLI. Before installing/using it, verify the Membrane CLI package and publisher (@membranehq) on npm and the project's GitHub to ensure you trust the maintainer. Installing `npm -g` packages runs code on your machine—if you prefer less risk, use `npx @membranehq/cli` or run the CLI in an isolated environment/container. Be aware the CLI will open a browser login flow and will manage credentials for connections; review Membrane's privacy/auth docs if you need to confirm where credentials are stored and how requests are proxied. If you have sensitive system data or strict policies, test in a sandbox first.Like a lobster shell, security has layers — review code before you run it.
latestvk973m5mn6me53p6zmbs9pf0h59842qfm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.