2Chat
v1.0.02Chat integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2Chat data.
⭐ 0· 31·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (2Chat integration) align with the instructions: the SKILL.md explains how to use the Membrane CLI to connect to 2Chat, discover actions, run actions, and proxy API requests. Nothing requested (no unrelated env vars or config paths) appears out-of-scope for a connector integration.
Instruction Scope
Runtime instructions stay focused on installing and using the Membrane CLI (login, connect, action list/run, proxy). They do not ask the agent to read arbitrary local files, environment variables, or send data to endpoints unrelated to Membrane/2Chat. The doc explicitly advises not to ask users for API keys and to let Membrane manage auth.
Install Mechanism
No formal install spec in the package registry (instruction-only), but SKILL.md instructs users to run a global npm install (npm install -g @membranehq/cli). That is a reasonable and expected mechanism for a CLI-based skill, but installing a global npm package executes third-party code on the host — users should trust the @membranehq package and review it before installing (or install in a container/sandbox).
Credentials
The skill declares no required env vars and relies on Membrane to perform authentication and token refresh. This is proportionate for a connector-style integration. Note: using the skill implicitly entrusts Membrane with authentication and request proxied data (including chat content), so evaluate trust/privacy of that third-party service.
Persistence & Privilege
Skill is instruction-only, not always-enabled, and does not request persistent system-wide privileges or try to modify other skills. It expects the user to run a CLI and perform browser-based auth; it does not demand autonomous always-on presence.
Assessment
This skill is coherent: it instructs the agent to use the Membrane CLI to connect to 2Chat and requires a Membrane account. Before installing or running commands: (1) verify you trust the @membranehq npm package (review its npm/GitHub page or run in a sandbox/container) because npm -g executes third-party code on your machine; (2) understand that authentication is handled by Membrane — Membrane will broker access to 2Chat and will see proxied request data (customer messages, etc.), so check their privacy/security policies; (3) do not manually share API keys with the skill — follow the documented connection flow; (4) if you need to limit risk, run the CLI in a restricted environment or inspect network traffic/permissions before use.Like a lobster shell, security has layers — review code before you run it.
latestvk977w17ee9ehhp6b072g0n6s418492ct
License
MIT-0
Free to use, modify, and redistribute. No attribution required.