Jellyreach
v1.0.2Jellyreach integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Jellyreach data.
⭐ 0· 112·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 (Jellyreach integration) match the instructions: all actions are performed via the Membrane CLI which is explicitly documented. Requiring a Membrane account and network access is reasonable for this integration.
Instruction Scope
SKILL.md directs the agent/user to run Membrane CLI commands (login, connect, action run, request). These commands perform network calls and open a browser for auth; they also proxy requests to Membrane, so Jellyreach requests and credentials are routed through getmembrane.com. This is coherent but has a privacy/centralization implication: data and auth are handled by Membrane rather than direct-to-Jellyreach API calls.
Install Mechanism
No automated install spec in the registry (instruction-only). The doc instructs users to install @membranehq/cli via npm -g. That is a typical, transparent step but requires installing a third-party global npm package; users should confirm they trust that package/source.
Credentials
The skill declares no required env vars or credentials and the instructions explicitly advise not to request API keys from users (use Membrane connections instead). The requested access is proportional to the stated function.
Persistence & Privilege
always is false and the skill is user-invocable; no indications it requests permanent agent-wide privileges or modifies other skills/configs. It relies on runtime CLI calls only.
Assessment
This skill delegates Jellyreach access to the Membrane platform (getmembrane.com) and instructs installing the @membranehq/cli npm package. Before installing or running it: 1) confirm you trust Membrane (review their privacy/security docs and the npm package), because requests and credentials will transit Membrane's service; 2) be aware you'll perform browser-based login (or copy/paste codes in headless environments) and that the CLI is a third-party global install; 3) if you prefer direct control, consider using a direct Jellyreach integration that uses your own API keys instead of a proxying service. If those tradeoffs are acceptable, the skill appears coherent and proportional to its purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97ff1akpfpa3571m7q5t3c42d8433dd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.