Melissa Data
v1.0.2Melissa Data integration. Manage data, records, and automate workflows. Use when the user wants to interact with Melissa Data data.
⭐ 0· 108·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
Name/description (Melissa Data integration) match the instructions: all actions are about discovering connectors/actions and proxying requests to Melissa Data via the Membrane CLI. Nothing requested appears unrelated to that purpose.
Instruction Scope
SKILL.md stays on-topic: it tells the agent to install and use the Membrane CLI, log in, create/connect to a Melissa Data connector, list and run actions, or proxy raw API requests. It does not instruct the agent to read arbitrary files, env vars, or system paths outside of using the CLI.
Install Mechanism
There is no formal install spec in the registry, but the instructions ask the user to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm package is a common pattern but does execute remote code on the host and persists a CLI binary; verify the package's authenticity and review its repository before installing.
Credentials
The skill declares no required env vars or credentials; authentication is delegated to Membrane. This is proportionate to the stated purpose, but it means credentials and API calls will be handled by a third-party service (Membrane) — users must trust that service to store/use their Melissa Data credentials appropriately.
Persistence & Privilege
Skill does not request always:true or special persistent privileges. The only persistent effect the instructions suggest is installing the Membrane CLI (user action), which is expected for this integration.
Assessment
This skill is coherent with its described purpose, but before using it: (1) decide whether you trust Membrane to handle your Melissa Data credentials and traffic (the CLI proxies requests through Membrane); (2) review the @membranehq/cli npm package and its GitHub repo to ensure it is legitimate and up-to-date before running a global install; (3) avoid sending sensitive or regulated data through the connector unless you’ve confirmed Membrane’s privacy/processing policies and that this workflow meets your compliance needs; (4) prefer running CLI commands interactively so you can inspect outputs and complete browser-based auth steps yourself.Like a lobster shell, security has layers — review code before you run it.
latestvk9787fe4mstt43pdpt5d39a0vx843tnh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.