Lime Crm

v1.0.0

Lime CRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lime CRM data.

0· 49·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description (Lime CRM integration) match the SKILL.md: it instructs the agent to use the Membrane CLI to connect, list actions, run actions, and proxy API requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, logging in via the browser, creating connections, listing/running actions, and proxying requests to Lime CRM. The doc explicitly advises against asking the user for API keys. It does require network access and a Membrane account, which is coherent with the stated purpose.
Install Mechanism
There is no packaged install spec in the registry (instruction-only). The SKILL.md recommends 'npm install -g @membranehq/cli' — a public npm package. Global npm installs modify system-global node locations (requires appropriate privileges) but that is expected to use the Membrane CLI.
Credentials
The skill requests no environment variables, no credentials, and no config paths. Authentication is delegated to Membrane (browser login / connection creation), which is proportionate for a proxy-based integration.
Persistence & Privilege
The skill is not always-enabled, does not modify other skills or system-wide settings, and is instruction-only (no bundled code). Autonomous invocation is allowed (platform default) but not combined with any broad credential requests.
Assessment
This skill is coherent: it only tells the agent to install and use the Membrane CLI to interact with Lime CRM and does not ask for unrelated secrets. Before installing, verify the @membranehq/cli npm package (owner, versions, and reviews) and confirm you trust Membrane as a proxy for your Lime CRM data, since Membrane will handle authentication and have access to the data you route through it. Be aware that 'npm install -g' requires write access to global node locations; run it only on machines where you control package installs. If you need greater assurance, review Membrane’s privacy/security docs and the CLI package source on the linked repository before proceeding.

Like a lobster shell, security has layers — review code before you run it.

latestvk977y65jsp82w6hvdx1024hd0d84f74t

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments