Uniify
v1.0.0Uniify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Uniify data.
⭐ 0· 97·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 (Uniify integration) matches the runtime instructions: all actions are performed via the Membrane CLI which proxies Uniify APIs and manages auth. The skill does not request unrelated credentials, binaries, or config paths.
Instruction Scope
Instructions are scoped to installing and using the Membrane CLI (login, create/list connections, run actions, and proxy requests). One noteworthy behavior: the documented 'membrane request' command can forward arbitrary paths to the Uniify API via the Membrane proxy, so the CLI (once authenticated) can perform any API calls the connected account permits — this is expected for an integration but worth awareness.
Install Mechanism
There is no automatic installer in the registry metadata; the SKILL.md recommends installing @membranehq/cli via npm (global install or npx). That is a standard public npm package install (moderate risk compared to no install), but installation is manual and traceable to the @membranehq package on npm/GitHub. Users should verify the package source before global install.
Credentials
The skill declares no required env vars or credentials and explicitly instructs users not to share API keys (advising to create Membrane connections instead). The lack of requested secrets is proportionate to the described behavior.
Persistence & Privilege
The skill is instruction-only, does not request persistent presence (always:false), and does not attempt to modify other skills or system-wide agent settings.
Assessment
This skill is coherent and does what it says: it teaches you to use the Membrane CLI to manage Uniify data. Before installing or running commands: (1) verify the legitimacy of the @membranehq package and its homepage/repository, (2) prefer using npx for one-off runs if you don't want a global npm install, (3) be aware that logging in grants the CLI the same permissions as the connected account and the 'membrane request' command can execute arbitrary API calls to Uniify via the proxy, and (4) avoid using high-privilege accounts until you trust the CLI and the Membrane service.Like a lobster shell, security has layers — review code before you run it.
latestvk97daq3axnya3d512ngx51w7fs84gkjk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.