Callrail
v1.0.2CallRail integration. Manage Companies. Use when the user wants to interact with CallRail data.
⭐ 0· 256·1 current·1 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
The name/description claim CallRail integration and the SKILL.md exclusively documents using the Membrane CLI to access CallRail actions and proxy API calls. The external dependency on the Membrane CLI is consistent with the stated purpose.
Instruction Scope
Instructions direct the user/agent to install and run the membrane CLI, log in, create/connect CallRail connectors, list/run actions, and optionally proxy arbitrary CallRail API requests via 'membrane request'. This is expected for a connector skill, but note that the proxy command allows arbitrary API calls to CallRail endpoints (so an agent could be used to send arbitrary data through the connection if permitted). The instructions do not request unrelated files, env vars, or system paths.
Install Mechanism
There is no automated install spec; this is instruction-only. The SKILL.md instructs users to install @membranehq/cli via 'npm install -g'. That is a reasonable requirement for using the described workflow, but installing global npm packages carries the usual supply-chain/trust considerations — users should verify the CLI package source and integrity before installing system-wide.
Credentials
The skill requests no environment variables or credentials in its metadata; authentication is delegated to the Membrane CLI/browser flow. This is proportionate to the stated purpose (a connector that relies on Membrane to manage credentials).
Persistence & Privilege
The skill is not always-enabled, does not request system config paths, and is instruction-only. It does not attempt to modify other skills or system-wide settings in the provided instructions.
Assessment
This skill is coherent: it expects you to install and log in to the Membrane CLI and then use that CLI to connect to CallRail. Before installing or using it, verify the @membranehq/cli package and the Membrane website are legitimate, run the CLI install in a controlled environment if you prefer (or use a per-user install), and review connector permissions when you authorize CallRail access. Be aware that the 'membrane request' proxy can send arbitrary API calls through your connector, so avoid giving the agent access to sensitive data unless you trust the account and connector being used. If you need higher assurance, inspect or obtain the Membrane CLI source/release you will install and revoke the connector credentials after testing.Like a lobster shell, security has layers — review code before you run it.
latestvk97eavekb4pwthe2g43g0vmjb1843p63
License
MIT-0
Free to use, modify, and redistribute. No attribution required.