Unifiedto
v1.0.2Unified.to integration. Manage data, records, and automate workflows. Use when the user wants to interact with Unified.to data.
⭐ 0· 128·1 current·1 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 promise (Unified.to integration) matches the instructions: all runtime steps use the Membrane CLI to create connections, list actions, run actions, or proxy requests to Unified.to. No unrelated services, credentials, or binaries are requested.
Instruction Scope
SKILL.md contains concrete CLI commands for installing and using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests. It does not instruct the agent to read arbitrary files or environment variables, nor to exfiltrate data to unexpected endpoints. It does instruct interactive browser-based login flows and headless alternatives, which are appropriate for auth flows.
Install Mechanism
There is no automated install spec in the registry (instruction-only). The README recommends installing @membranehq/cli via 'npm install -g', which is a reasonable, traceable public npm package but has the usual considerations for global npm installs (admin rights, global PATH modification). Because installation is manual/recommended rather than automatic, the skill itself does not write code to disk.
Credentials
The skill declares no required env vars, no config paths, and requests no credentials. The SKILL.md explicitly advises letting Membrane handle credentials instead of asking for API keys. This is proportional to the described purpose.
Persistence & Privilege
always is false and the skill does not request persistent presence or modify other skills or system-wide settings. It is an instruction-only skill that relies on a separate CLI for any stateful auth, so it does not itself obtain elevated privileges.
Assessment
This skill is coherent and appears to be what it says: it instructs use of the Membrane CLI to talk to Unified.to. Before installing/using it: (1) verify you trust the @membranehq/cli npm package (check the npm page, maintainer, and GitHub repo) because the SKILL.md recommends a global npm install; (2) be aware that using 'membrane request' proxies requests through Membrane—do not send sensitive secrets or host-internal endpoints through the proxy unless you trust Membrane's service and privacy model; (3) follow the browser/headless login steps to authenticate rather than providing API keys to the skill; and (4) because the skill can be invoked autonomously by the agent (normal platform behavior), only enable it if you trust that the agent may call these CLI patterns. If you want higher assurance, inspect the upstream CLI project code and Membrane's documentation before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97b3bfb60bjsbzrva124v53yx842r4x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.