Ubiq Security
v1.0.0Ubiq Security integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ubiq Security data.
⭐ 0· 61·0 current·0 all-time
byMembrane Dev@membranedev
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 say it integrates with Ubiq Security and all runtime instructions revolve around using the Membrane CLI to discover connectors, create connections, run actions, or proxy requests. Requesting a Membrane account and the Membrane CLI is coherent with the stated purpose.
Instruction Scope
SKILL.md instructs only on installing and using the Membrane CLI, performing connector discovery, running actions, and proxying API requests. It does not ask the agent to read unrelated files, environment variables, or system-wide configuration, nor to transmit data to unexpected endpoints beyond Membrane/Ubiq APIs.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the doc instructs users to run `npm install -g @membranehq/cli` (and also demonstrates `npx`). Installing a global npm package is a standard way to obtain the CLI but carries the usual npm risks (third-party code executed on install). Prefer npx or verifying the package source/signature if you are concerned.
Credentials
The skill declares no required env vars or credentials and explicitly advises letting Membrane handle credentials server-side. No unrelated secrets or system config paths are requested.
Persistence & Privilege
The skill is not forced-always, does not request special system privileges, and is user-invocable. It does not modify other skills or agent-wide configuration in the instructions.
Assessment
This is an instruction-only integration that uses the Membrane CLI to access Ubiq Security connectors — that is coherent for its purpose. Before installing or running the CLI: (1) verify you trust the @membranehq/cli npm package (consider using `npx` to avoid a global install or check the package on the npm registry/GitHub); (2) review the permissions and scopes Membrane requests during login because Membrane will broker access to your Ubiq Security account; (3) avoid pasting secrets into chat — follow the connection flow so Membrane stores credentials server-side; and (4) if you need stronger isolation, run the CLI in a controlled environment (container or ephemeral VM).Like a lobster shell, security has layers — review code before you run it.
latestvk97dn5ybxmy56brkt17v3wj0h584a0m9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.