Ringcentral
v1.0.2RingCentral integration. Manage Users, Persons, Organizations, Leads, Deals, Projects and more. Use when the user wants to interact with RingCentral data.
⭐ 0· 94·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
Name/description match the instructions: the SKILL.md explains how to connect to RingCentral via the Membrane CLI and run RingCentral actions. No unrelated credentials, binaries, or system paths are requested.
Instruction Scope
Instructions stay within the stated purpose (install CLI, login, create/connect, list/run actions, proxy requests). Important: requests and credentials are proxied through the Membrane service (getmembrane.com), so RingCentral traffic and tokens will pass through that third party—users should be aware of that data flow.
Install Mechanism
There is no platform install spec in the registry (instruction-only), but the SKILL.md tells users to run 'npm install -g @membranehq/cli'. Installing a global npm package is a reasonable requirement for a CLI-driven skill, but verify the package identity and source before installing and avoid running as an unprivileged user where possible.
Credentials
The skill declares no required env vars or credentials; authentication is handled by Membrane (browser login/connection flow). This is proportionate, but it implies you trust Membrane to store/refresh RingCentral credentials on your behalf.
Persistence & Privilege
Skill does not request always:true, does not modify other skills, and is user-invocable. Default autonomous invocation is allowed (platform default) and is not in itself a concern here.
Assessment
This skill is coherent: it instructs you to use the Membrane CLI to interact with RingCentral. Before installing/using it, verify the @membranehq/cli package on the npm registry (publisher, download counts, repo), review Membrane's privacy/security docs because your RingCentral tokens and request payloads will transit through their service, and avoid installing global packages as root. If you need stricter control of credentials, consider creating a dedicated Membrane tenant/account or using an alternative integration where you retain direct control of the API credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97323kxn6mx20f5fyb24p8zbn842jjw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.