Liondesk
v1.0.2Liondesk integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more. Use when the user wants to interact with Liondesk data.
⭐ 0· 98·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 match the instructions: the SKILL.md explains how to use the Membrane CLI to connect to Liondesk, list actions, run actions, and proxy requests. Nothing in the skill requests unrelated capabilities or secrets.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, creating a connection, discovering actions, and proxying requests. They explicitly delegate credential handling to Membrane. Note: using the skill requires a Membrane account and results in Membrane having access to Liondesk credentials/data (expected for a proxy-based integration).
Install Mechanism
This is an instruction-only skill (no install spec or code). It recommends installing @membranehq/cli globally via npm and occasionally using npx. Installing a global npm package or running npx pulls code from the public registry — normal for CLI usage but requires trust in the @membranehq package publisher and the package contents.
Credentials
The skill declares no required env vars, no config paths, and no primary credential. It relies on Membrane to manage authentication, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-enabled and does not request elevated persistence. It is user-invocable and allows autonomous invocation by default (platform default), which is expected for a skill of this type.
Assessment
This skill is coherent: it instructs you to install and use the official Membrane CLI to connect to Liondesk and relies on Membrane to store/refresh credentials. Before proceeding: 1) Verify the @membranehq npm package and the Membrane service (publisher, GitHub repo, homepage) to ensure you trust the vendor. 2) Be aware that creating a connection gives Membrane access to your Liondesk data/credentials — review the OAuth scopes or permissions requested when you connect. 3) Prefer installing the CLI in an isolated environment (container or VM) if you are cautious about global npm installs or running npx. 4) Limit the Membrane connection's privileges and, if possible, test with a non-production account. 5) Do not expect any hidden local exfiltration from this skill: it does not ask for local secrets or extra env vars, but it does centralize access through Membrane, so your primary trust decision is whether to trust that service.Like a lobster shell, security has layers — review code before you run it.
latestvk97f1a4qpgwavwph9ttzanx2gn842yq8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.