Campaign Cleaner
v1.0.2Campaign Cleaner integration. Manage data, records, and automate workflows. Use when the user wants to interact with Campaign Cleaner data.
⭐ 0· 64·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 skill's name/description match the instructions: it explains how to use the Membrane CLI to manage Campaign Cleaner data and automation. Required capabilities (network access and a Membrane account) are consistent with the stated purpose; there are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in via browser, creating connections, listing actions, running actions, and proxying requests through Membrane. The instructions do not ask the agent to read unrelated files, secrets, or system configuration.
Install Mechanism
There is no formal install spec, but the SKILL.md instructs users to run 'npm install -g @membranehq/cli'. Installing a global npm package is a reasonable step for this integration, but it does introduce the usual trust risk of executing third-party code from the npm registry. The skill itself does not write files or include external URLs beyond recommending the official package.
Credentials
The skill requests no environment variables or credentials in its metadata and explicitly recommends not asking users for API keys because Membrane manages auth. This is proportionate to the described functionality; the only credential flow is the browser-based Membrane login/connector flow.
Persistence & Privilege
The skill does not request always-on presence and leaves autonomous invocation enabled (the platform default). It does not instruct modifying other skills or system-wide agent settings.
Assessment
This skill is internally consistent, but before installing: (1) confirm you trust the Membrane service and the @membranehq/cli npm package (review the package/repo and publisher), (2) be aware installing with 'npm install -g' adds a global binary to your system—use a controlled environment if concerned, (3) understand that connecting via Membrane routes API calls and credentials through Membrane (so Campaign Cleaner data will be visible to that service), and (4) verify privacy and data handling terms with Membrane if you will proxy sensitive campaign data. Absence of scanner findings only means there was no code to analyze in the skill bundle, not that the external CLI is risk-free.Like a lobster shell, security has layers — review code before you run it.
latestvk972tahmvwf0q1e33nrpe0swb1843r5j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.