Justcall
v1.0.2JustCall integration. Manage Persons, Organizations, Leads, Activities, Notes, Files and more. Use when the user wants to interact with JustCall data.
⭐ 0· 117·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/description (JustCall integration) matches the instructions (use Membrane CLI to connect and run JustCall actions). Minor bookkeeping inconsistency: the registry metadata lists no required binaries, but the SKILL.md instructs installing the @membranehq/cli npm CLI — this is expected for the integration but should have been declared.
Instruction Scope
Instructions stay within the stated purpose (install Membrane CLI, login, create/inspect connections, run actions, or proxy requests to JustCall). Important privacy/security note in the instructions: requests and credential handling are proxied through Membrane's servers — the user should understand that connection data and API requests will transit Membrane.
Install Mechanism
There is no automated install spec in the registry (lowest platform risk), but SKILL.md instructs running `npm install -g @membranehq/cli`. Installing a global npm package is a typical approach but carries the usual moderate risk of third-party packages — verify the package publisher and review package metadata before installing.
Credentials
The skill declares no required environment variables or secrets and explicitly instructs not to request user API keys (it delegates auth to Membrane). The requested scope is proportional to a connector-style integration.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges and is user-invocable only. There is no instruction to modify other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: use Membrane's CLI to interact with JustCall. Before installing/use: (1) confirm you trust Membrane as the intermediary (requests and tokens are proxied through their service and may be visible to them); (2) verify the npm package @membranehq/cli on the npm website and that the publisher/repo matches getmembrane.com or the referenced GitHub; (3) prefer running the CLI in an isolated environment if you have concerns; (4) do not paste unrelated secrets — follow the SKILL.md headless login flow; and (5) note the small metadata mismatch (CLI requirement not declared) — this is not a functional problem but worth being aware of.Like a lobster shell, security has layers — review code before you run it.
latestvk97dwwfhxfreh05bwe4411e6g98427t1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.