Quickemailverification
v1.0.2QuickEmailVerification integration. Manage data, records, and automate workflows. Use when the user wants to interact with QuickEmailVerification data.
⭐ 0· 118·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's stated purpose (integrate with QuickEmailVerification) matches the instructions (use Membrane to create a connection, list/run actions, or proxy requests). However, the SKILL.md instructs installing the @membranehq/cli via npm -g (requires Node/npm and a network install), but the registry metadata declared no required binaries — a metadata omission rather than a functional mismatch.
Instruction Scope
Instructions are scoped to interacting with QuickEmailVerification through Membrane: login, create/inspect connections, list/run actions, and proxy HTTP requests. The guidance does not ask the agent to read arbitrary local files or request unrelated environment variables. It does require interactive authentication (browser flow or headless completion) and allows arbitrary proxied API calls to the QuickEmailVerification API via Membrane.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but SKILL.md recommends installing the Membrane CLI with `npm install -g @membranehq/cli`. Global npm installs are common but have supply-chain considerations; the registry does not validate the npm package integrity or pin a release. This is not inherently malicious but is a relevant operational detail the user should verify before installing.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs not to ask users for API keys, relying on Membrane to manage auth. This is proportionate: a connector-based integration typically delegates credential management to the integration platform. It does require a Membrane account and network access.
Persistence & Privilege
The skill is not marked always:true and is user-invocable; it does not request persistent system-wide privileges or modify other skills. Being instruction-only, it does not install persistent agents itself (though installing the Membrane CLI is an optional user action).
Assessment
This skill appears to do what it says: it uses Membrane to connect to QuickEmailVerification and run or proxy API actions. Before installing/using it: (1) Be aware you will likely need Node/npm to install the recommended Membrane CLI (`npm install -g @membranehq/cli`) — verify the package name and its publisher on npm and GitHub first. (2) You will authenticate via a browser flow to your Membrane account; Membrane will hold the QuickEmailVerification credentials on your behalf, so verify you trust Membrane's service and review its privacy/security docs. (3) The Membrane proxy can send arbitrary requests to the target API under your connection, so ensure the account you connect has only the permissions you intend and avoid sending sensitive data unless necessary. (4) The registry metadata omits the CLI requirement; expect to install the CLI manually or ensure your environment already has it. If you need higher assurance, inspect the @membranehq/cli source/release on GitHub and the QuickEmailVerification connector definition before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97bqxnh3pa25z10n8z5sszq6x8428xg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.