Zamzar
v1.0.0Zamzar integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zamzar data.
⭐ 0· 49·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
medium confidencePurpose & Capability
Name/description promise Zamzar integration and the SKILL.md consistently instructs using the Membrane CLI to connect to Zamzar. Requiring the Membrane CLI is coherent with the stated approach, but it does change the data path (requests and credentials are proxied through Membrane rather than the agent calling Zamzar directly).
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, logging in, creating a connection, listing/running actions, and optionally proxying requests to the Zamzar API. The instructions do not ask the agent to read unrelated files or environment variables.
Install Mechanism
The skill recommends a global npm install (npm install -g @membranehq/cli) and uses npx in examples. Global npm installs run arbitrary package install scripts and write to disk — a common but higher‑risk install mechanism than instruction‑only skills. The package name and repo appear plausible, but you should verify the npm package and repository before installing.
Credentials
The skill does not request local environment variables or secrets. However, it requires a Membrane account and uses Membrane to hold and refresh Zamzar credentials server‑side — meaning Membrane (a third party) will have access to the connected Zamzar account. That is proportionate to the described design but worth explicit consent and trust.
Persistence & Privilege
The skill is instruction‑only, has no install spec that writes files itself, and does not request always:true or other elevated platform privileges. It does rely on the user to install the Membrane CLI; autonomous model invocation remains possible but is the platform default and not unique to this skill.
Assessment
This skill is coherent: it tells the agent to use the Membrane CLI to work with Zamzar. Before installing or using it, verify you trust Membrane (review the npm package and GitHub repo, check package maintainers, and confirm privacy/terms) because your Zamzar credentials and traffic will be proxied through their service. Installing @membranehq/cli globally will run code on your machine — prefer using npx or a local install if you want less system impact, or inspect the package source first. If you plan to allow autonomous agent actions, remember the agent could run membrane commands that affect your Zamzar data, so only enable that capability if you trust the skill and Membrane account being used.Like a lobster shell, security has layers — review code before you run it.
latestvk97c0gr3jjyaswbd15237h6b0n84fwtw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.