Myphoner
v1.0.2Myphoner integration. Manage Leads, Persons, Organizations, Pipelines, Users, Roles and more. Use when the user wants to interact with Myphoner data.
⭐ 0· 93·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
medium confidencePurpose & Capability
The skill claims to integrate with Myphoner and all runtime instructions use the Membrane CLI and Membrane proxy to perform Myphoner API calls — this is consistent with the description. However, the registry metadata lists no required binaries even though SKILL.md instructs installing the @membranehq/cli (npm) and running the `membrane` command; the skill should have declared that dependency.
Instruction Scope
Instructions are narrowly scoped to installing the Membrane CLI, authenticating via Membrane, listing/connecting actions, running proxy requests, and running Myphoner-related actions. A notable operational detail: proxied requests and credential management happen server-side at Membrane, so Myphoner data and auth tokens will be sent to/handled by the Membrane service — this is expected for this integration but worthy of user awareness.
Install Mechanism
There is no formal install spec in the registry, but SKILL.md tells users to run `npm install -g @membranehq/cli` (and sometimes uses npx). Installing a public npm CLI is a common pattern, but it is an out-of-band install step not captured in the metadata. Verify the npm package and upstream repo before installing global packages.
Credentials
The skill declares no environment variables or credentials and the instructions explicitly instruct not to ask users for API keys (Membrane manages credentials). That matches the runtime flow: authentication is handled by Membrane rather than local env vars.
Persistence & Privilege
The skill does not request always:true and does not attempt to modify other skills or system-wide settings. It relies on external Membrane account/session state (browser login), which is normal for CLI-based OAuth flows.
Assessment
Before installing: (1) Understand that this skill requires you to install and use the Membrane CLI (npm package) and to authenticate via Membrane; that means API calls and auth tokens will be proxied through Membrane's service. (2) Confirm you trust getmembrane.com / the @membranehq npm package and review its GitHub repo or package source if possible. (3) Note the registry metadata did not declare required binaries — you'll need npm/node and a browser (or a headless code flow). (4) In sensitive environments, avoid installing global npm packages or run them in isolated containers; verify Membrane's privacy/security docs and the exact permissions you grant during the OAuth flow.Like a lobster shell, security has layers — review code before you run it.
latestvk97ab7typk3bcaatsvzvpj8n2n843jbn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.