Leadgenius
v1.0.2LeadGenius integration. Manage data, records, and automate workflows. Use when the user wants to interact with LeadGenius data.
⭐ 0· 78·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
Name/description say this integrates with LeadGenius and the SKILL.md exclusively instructs using the Membrane CLI and Membrane connections to access LeadGenius — the requested capabilities line up with the stated purpose.
Instruction Scope
Runtime instructions stay focused on installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to LeadGenius. There are no instructions to read unrelated files, gather unrelated environment variables, or exfiltrate data to unmentioned endpoints.
Install Mechanism
The SKILL.md tells users to install @membranehq/cli via npm (global) and uses npx in examples. This is expected for a CLI-driven skill, but the skill metadata has no install spec. Installing a global npm package modifies the host environment and pulls code from the public npm registry — verify package authenticity (package name, publisher, and npm page) before installing.
Credentials
The skill declares no required env vars or credentials and explicitly defers auth to Membrane (which the instructions say manages credentials server-side). The lack of requested secrets is proportionate to the use of a hosted connector flow.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent agent-level privileges or modifications to other skills. The default ability for the agent to invoke the skill autonomously is standard and not, by itself, a red flag here.
Assessment
This skill is instruction-only and uses the Membrane CLI to access LeadGenius. Before installing or using it: 1) Verify the npm package @membranehq/cli is the official package and check the publisher and README on the npm registry; 2) Be aware that npm -g alters your system PATH and that the CLI may create local config files (inspect where it stores tokens or config after login); 3) The skill instructs you to authenticate in a browser to create a connection — review the Membrane and LeadGenius privacy/security docs to understand what access you grant; 4) If you need stronger isolation, run the CLI in a sandbox/container or on a dedicated machine; 5) Because the skill has no declared install in registry metadata, treat the SKILL.md instructions as the authoritative install steps and confirm they match official Membrane docs and repository links before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97215tb0nedsdndhefpdr0dwn842zb4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.