Cliengo
v1.0.2Cliengo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cliengo data.
⭐ 0· 106·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
Name/description describe a Cliengo integration and the SKILL.md exclusively instructs use of the Membrane CLI to connect to Cliengo, list actions, run actions, and proxy API requests — these requirements are appropriate for the stated purpose.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, authenticating via Membrane, creating/listing connections, running actions, and proxying requests to Cliengo. The SKILL.md does not instruct reading unrelated local files, scanning system configs, or exfiltrating data to unknown endpoints.
Install Mechanism
The skill recommends installing @membranehq/cli via npm -g. This is a public npm package (moderate risk compared to no-install skills). Installing a global npm package writes code to disk and may require elevated permissions — verify the package/source (getmembrane.com / @membranehq) before installing.
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane to manage Cliengo credentials via a browser-based login flow, which is proportionate to the integration and avoids requesting unrelated secrets.
Persistence & Privilege
The skill is instruction-only, has no 'always' flag, and does not request persistent system-wide privileges or attempt to modify other skills. It will only run commands when invoked (subject to the agent's normal autonomous-invocation policy).
Assessment
This skill uses the Membrane CLI to talk to Cliengo and does not request unrelated secrets — that makes it internally consistent. Before installing, verify the Membrane project and npm package (@membranehq/cli) are legitimate (check getmembrane.com and the GitHub repo), and prefer installing in a controlled environment (or without -g) if you are cautious about global npm installs. Be aware you'll need a Membrane account and will authenticate via a browser flow; never paste your raw API keys into chat unless you explicitly trust the destination. If you don't trust the external Membrane service, don't install or run the CLI.Like a lobster shell, security has layers — review code before you run it.
latestvk9748jkxzzzkgpxt7d6vrpr0hh843ykw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.