Emaillistverify
v1.0.2EmailListVerify integration. Manage Users. Use when the user wants to interact with EmailListVerify data.
⭐ 0· 69·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 (EmailListVerify integration) matches the SKILL.md: all runtime steps center on using the Membrane CLI to discover connectors, create connections, run actions, or proxy requests to EmailListVerify. No unrelated services, credentials, or binaries are requested.
Instruction Scope
Instructions tell the agent to install and use the Membrane CLI, perform login flows, list/connect actions, run actions, and proxy raw API calls. This stays within the stated purpose. One important operational note: using the proxy routes EmailListVerify data through Membrane — the skill advises this, but users should be aware that request/response data will transit Membrane's servers.
Install Mechanism
The skill is instruction-only (no install spec), but it instructs installing @membranehq/cli via `npm install -g`. Installing a global npm package is a standard approach but executes third-party code on the machine — verify the package identity and trustworthiness before installing.
Credentials
The skill declares no required environment variables or credentials. It does require a Membrane account and network access, which is proportional because Membrane handles auth and proxying. There are no requests for unrelated secrets or local config paths.
Persistence & Privilege
The skill does not request persistent or elevated presence (always: false) and contains no install-time actions in the registry metadata. The agent may invoke the skill autonomously by default, which is platform-standard behavior.
Assessment
This skill appears to do what it says: it relies on the Membrane CLI to access EmailListVerify. Before using it, verify you trust the @membranehq/cli package and the Membrane service (review their homepage, repository and privacy/security docs), because API requests and data will be proxied through Membrane's infrastructure. Be cautious installing global npm packages (they run third-party code on your machine). When authenticating, check the permissions requested in the browser flow. If you need stronger guarantees, inspect the Membrane CLI source or run it in an isolated environment (container/VM) and confirm that the connector IDs and endpoints correspond to official EmailListVerify APIs.Like a lobster shell, security has layers — review code before you run it.
latestvk976atwre0rvzx4q3adbts5xn58421s7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.