Leadboxer
v1.0.2LeadBoxer integration. Manage Leads, Persons, Organizations, Deals, Activities, Notes and more. Use when the user wants to interact with LeadBoxer data.
⭐ 0· 99·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 name/description (LeadBoxer integration) match the runtime instructions: all actions are performed through the Membrane CLI and the skill guides creating a connector, running actions, and proxying API requests to LeadBoxer.
Instruction Scope
SKILL.md only instructs the agent/user to install and run the Membrane CLI, authenticate via browser, list/connect to connectors, run actions, and proxy requests. It does not ask the agent to read unrelated files, environment variables, or exfiltrate data to unexpected endpoints. Note: proxying allows arbitrary requests to LeadBoxer endpoints (expected for this integration).
Install Mechanism
There is no formal install spec in the registry, but SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a public npm CLI is a standard, moderate-risk method; however the skill metadata declares 'required binaries: none' even though Node/npm and the membrane binary will be required — a documentation mismatch to verify.
Credentials
The skill declares no required environment variables or credentials and explicitly defers auth to Membrane. That is proportional: integrating with LeadBoxer via Membrane reasonably requires a Membrane account and connector authentication but not extra unrelated secrets.
Persistence & Privilege
always:false and autonomous invocation is allowed (platform default). The skill does not request persistent system-wide privileges or modify other skills. Be aware an agent with permission to invoke the skill could run Membrane commands which will perform network operations under the authenticated Membrane connection (expected for this type of integration).
Assessment
This skill appears consistent with a LeadBoxer integration that uses the Membrane CLI. Before installing: ensure you trust the @membranehq/cli package (verify npm/package homepage and publisher), confirm you have Node/npm and are comfortable installing a global npm CLI, and be prepared to authenticate a Membrane account in a browser (the connector grants Membrane access to LeadBoxer data). Note the registry metadata does not list required binaries (Node/npm or the membrane binary) — verify those prerequisites. Finally, consider that any agent invocation of this skill (automated or manual) can run proxy requests and actions against your LeadBoxer data via Membrane, so limit who or what can invoke the agent and review connector scopes/permissions in your Membrane account.Like a lobster shell, security has layers — review code before you run it.
latestvk972paex8gx6k96twk12nh4n7d842wrm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.