Amocrm
v1.0.2AmoCRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with AmoCRM data.
⭐ 0· 128·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 and description match the instructions: the skill delegates AmoCRM access to the Membrane platform and instructs using the Membrane CLI. Asking users to install and use a connector and connection IDs is appropriate for an integration skill.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, performing login via browser, listing/connecting connectors, running actions, and proxying AmoCRM API requests. It does not instruct reading unrelated files or exposing unrelated credentials.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to run `npm install -g @membranehq/cli` or use `npx`, which is expected for a CLI-based integration but carries the usual third-party npm package risk—installing global npm packages executes remote code. Verify you trust @membranehq and the package source before installing.
Credentials
The skill declares no required env vars or credentials and explicitly instructs not to ask users for AmoCRM API keys, instead relying on Membrane-managed connections. That is proportionate to the stated purpose.
Persistence & Privilege
Skill metadata does not request always:true or other elevated persistence. It is user-invocable and requires interactive login via browser; it does not modify other skills or system-wide configs.
Assessment
This skill appears coherent: it relies on the Membrane CLI to proxy AmoCRM calls so you don't provide raw API keys. Before installing/using it: (1) confirm you trust the @membranehq npm package and getmembrane.com (installing global npm packages runs remote code); (2) review Membrane's privacy/TOS to understand how it stores/uses your AmoCRM credentials; (3) create least-privilege connections on AmoCRM if possible; and (4) if you prefer not to install global packages, use `npx` per the instructions. If you need greater assurance, inspect the Membrane CLI repository/releases and the connector implementation before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97d3fn8ka3jjrvkn54dtf263x842fs6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.