Zoho Cliq
v1.0.2Zoho Cliq integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho Cliq data.
⭐ 0· 71·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
The name and description (Zoho Cliq integration) match the instructions: all actions are performed via the Membrane CLI and Membrane-managed connectors. Nothing in the SKILL.md asks for unrelated cloud credentials or unrelated system access.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, creating a connector, listing and running actions, and proxying requests. The SKILL.md will cause the user/agent to authenticate via Membrane and send API requests through Membrane's proxy — so data and API calls will transit Membrane's service (expected for this design). There is no instruction to read unrelated local files or environment variables.
Install Mechanism
There is no formal install spec in the registry, but the SKILL.md instructs installing a global npm package (@membranehq/cli). Installing a global npm CLI is common for this usage, but it does execute third-party code on the host — verify the package source and trustworthiness before installing.
Credentials
The skill declares no required env vars or credentials because Membrane handles authentication. This is proportionate to the stated purpose. Be aware credentials will be stored/managed by the Membrane CLI/account, not by this skill.
Persistence & Privilege
The skill is user-invocable and not always-enabled; it does not request elevated platform privileges or to modify other skills. Autonomous invocation (model invocation enabled) is the platform default and not flagged here.
Assessment
This skill delegates authentication and API calls to the Membrane CLI/service. Before installing or using it: (1) confirm you trust the @membranehq/cli npm package and the Membrane service (data and API requests will transit their infrastructure), (2) prefer installing the CLI in a controlled environment or verifying the package integrity (source repo, npm publisher), (3) understand that authentication tokens will be managed by Membrane CLI (check where it stores tokens), and (4) avoid installing global npm packages on sensitive systems unless you trust the vendor. If you need stronger guarantees, review the referenced GitHub repository and the Membrane product documentation first.Like a lobster shell, security has layers — review code before you run it.
latestvk97960dxew0d32t1h92bkz7h7n8433ry
License
MIT-0
Free to use, modify, and redistribute. No attribution required.