Orbisx
v1.0.2OrbisX integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with OrbisX data.
⭐ 0· 63·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 (OrbisX integration) aligns with the instructions (use Membrane CLI to connect to OrbisX). Minor incoherence: registry metadata lists no required binaries, but SKILL.md clearly requires the Membrane CLI be installed.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI to authenticate, create connections, list/run actions, and proxy requests to OrbisX. Nothing in the instructions directs reading unrelated local files or asking for unrelated credentials.
Install Mechanism
There is no embedded install spec (instruction-only), but SKILL.md asks the user to run `npm install -g @membranehq/cli`. Using a public npm package is a normal choice for a CLI install but carries the usual supply-chain considerations — moderate risk compared to no install.
Credentials
The skill does not require environment variables, secrets, or config paths. It relies on Membrane for auth rather than asking for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always-on presence and does not modify other skills or system settings. It follows normal agent invocation behavior.
Assessment
This skill is an instruction-only integration that expects you to install and use the official Membrane CLI to access OrbisX. Before installing: (1) verify the @membranehq/cli package on npm and the getmembrane.com project are legitimate and current, (2) be aware you will need a Membrane account and to complete browser-based authentication, and (3) understand that the Membrane proxy can send arbitrary API requests on your behalf — only use it if you trust the Membrane service and the OrbisX tenant you connect to. The only minor mismatch is that the registry metadata didn't list the required CLI binary; that's likely an oversight but worth noting. If you have strict supply-chain or global npm install policies, review the Membrane CLI source and permissions before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97c4eajb46xxgpx81zt9da069842cta
License
MIT-0
Free to use, modify, and redistribute. No attribution required.