Ongage
v1.0.2Ongage integration. Manage Accounts. Use when the user wants to interact with Ongage data.
⭐ 0· 130·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
The name/description (Ongage integration) matches the instructions: all commands target the Membrane CLI and Ongage via Membrane's proxy. The need for a Membrane account and the CLI is coherent with the stated purpose.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI (login, create connection, run actions, proxy requests). One important behavioral note: proxying requests via Membrane means request payloads and resulting data will be sent to Membrane's servers — the instructions explicitly rely on that and advise against asking users for raw API keys.
Install Mechanism
This is an instruction-only skill (no install spec). It instructs the user to run `npm install -g @membranehq/cli`, which will install a third-party global npm package. Installing global packages modifies the system and runs third-party code — expected for a CLI integration but requires you to trust the package and its publisher.
Credentials
The skill declares no required env vars or credentials. It delegates authentication to Membrane (no local API keys requested), which is proportionate to the stated approach. The tradeoff is that Membrane holds the credentials/refresh tokens server-side.
Persistence & Privilege
The skill does not request always:true and does not attempt to persist or modify other skills or system-wide settings. It is user-invocable and can be invoked autonomously (platform default).
Assessment
This skill delegates Ongage access to the Membrane service and asks you to install the @membranehq/cli package. Before installing/use: (1) Verify the npm package and its publisher (review the package on npm and its GitHub repo) to ensure you trust the code you will run globally; (2) Understand that using the proxy sends requests and data (including any personal or campaign data) through Membrane's servers — read their privacy/security docs and ensure that meets your requirements; (3) Prefer installing the CLI in an isolated environment or using npx if you want to avoid a global install; (4) If you need strict data residency or you cannot trust a third party with credentials, consider using direct Ongage API integration instead. If you want me to, I can fetch the package repo and recommend checks to validate the CLI before you install it.Like a lobster shell, security has layers — review code before you run it.
latestvk9794mv9acycmk6n30jrcnb11h843hg0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.