Callfire
v1.0.2CallFire integration. Manage data, records, and automate workflows. Use when the user wants to interact with CallFire data.
⭐ 0· 116·0 current·0 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
Name/description match the instructions: the SKILL.md consistently describes using Membrane to access CallFire (actions, contacts, broadcasts). The only prerequisite is network access and a Membrane account, which aligns with the described functionality.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI (login, connect, list actions, run actions, and proxy requests). They do not ask the agent to read unrelated files or environment variables, nor to transmit data to unexpected external endpoints beyond the CallFire API via Membrane's proxy.
Install Mechanism
This is an instruction-only skill (no install spec in the registry), but SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal way to get the CLI but carries the usual moderate risk of installing third-party code; users should vet the npm package and prefer non-global or sandboxed installs on multi-user systems.
Credentials
The skill declares no required env vars and relies on browser-based Membrane authentication; this is proportionate. Note that Membrane will hold and refresh API credentials on behalf of the user, so installing/using the CLI grants Membrane access to CallFire data once a connection is created.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges. It is user-invocable and relies on the Membrane CLI for auth/requests; there is no indication it attempts to modify other skills or system-wide agent settings.
Assessment
This skill simply documents how to use the Membrane CLI to talk to CallFire and appears coherent. Before installing/using it: 1) Verify the @membranehq/cli npm package and the getmembrane.com / GitHub project are legitimate and up-to-date; avoid global npm installs on shared machines (use a container, VM, or per-user install). 2) Understand that completing the Membrane login will grant Membrane (and thus the CLI) access to your CallFire account — use a least-privilege account or review the permissions requested. 3) Be aware the proxy command can send arbitrary API requests to CallFire, so only run commands you trust. If you need higher assurance, inspect the Membrane CLI source code or run it in an isolated environment before granting production credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk972tt5k9e3361wjp884r6mmph843kqv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.