Leadpops
v1.0.1Leadpops integration. Manage Leads, Users, Organizations, Projects, Activities, Notes and more. Use when the user wants to interact with Leadpops data.
⭐ 0· 105·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
The name/description state a Leadpops integration and the SKILL.md consistently instructs using the Membrane CLI to connect, list actions, run actions, and proxy API requests — all reasonable for this purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions remain scoped to installing and using the Membrane CLI, performing OAuth-style login, creating connections, listing/running actions, and proxying requests. The guidance explicitly discourages asking users for API keys and does not instruct reading unrelated files or environment variables.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm CLI is a common pattern but does involve pulling code from the npm registry and writing to the system PATH — verify the package identity (publisher, GitHub repo) before installing.
Credentials
The skill declares no required environment variables or primary credential. Authentication is delegated to Membrane (browser OAuth flow), which is appropriate for a connector-style integration. No unrelated secrets are requested.
Persistence & Privilege
The skill is not always-on and does not request elevated platform privileges. It is instruction-only and does not modify other skills or system-wide agent settings. Normal autonomous invocation is allowed by default (not a problem alone).
Assessment
This skill is coherent: it instructs the agent to use the Membrane CLI to talk to Leadpops and does not request local secrets. Before installing/using it, verify you trust the Membrane project (@membranehq on npm and the linked GitHub repo), since the CLI will run locally and Membrane will broker access to your Leadpops account (they handle tokens server-side). Installing the CLI globally will modify your system PATH and may require elevated privileges — prefer reviewing the CLI source or installing in a controlled environment if you have concerns. Finally, be aware that once connected, the Membrane proxy can issue arbitrary API calls on behalf of the connected account, so only create connections for accounts you trust and review activity as needed.Like a lobster shell, security has layers — review code before you run it.
latestvk9759rgefc9hgy66y50g8hrmnh843qgm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.