Rocket Chat
v1.0.2Rocket Chat integration. Manage Users, Rooms, Teams, Integrations. Use when the user wants to interact with Rocket Chat data.
⭐ 0· 91·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 (Rocket Chat integration) match the SKILL.md: all instructions relate to discovering connectors, creating connections, running actions, and proxying requests to Rocket.Chat via the Membrane service. Nothing requested is unrelated to that purpose.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI and its commands (login, connection list, action list/run, request). They do not read local files or ask for local credentials. Important caveat: proxying through Membrane means request payloads, API calls, and any data sent will traverse Membrane's servers — the SKILL.md explicitly relies on that behavior.
Install Mechanism
The skill is instruction-only (no install spec). The docs instruct users to run `npm install -g @membranehq/cli` which is a normal workflow but does pull code from the public npm registry. There is no automatic install performed by the skill bundle itself.
Credentials
The skill declares no required env vars or credentials and the instructions rely on an interactive Membrane login flow rather than local secrets. This is proportionate to a connector-oriented integration.
Persistence & Privilege
always is false and no install spec writes files on install; the skill does allow autonomous invocation by default (platform default) but there are no additional privileged settings or persistent configuration changes required by the skill itself.
Assessment
This skill appears to do what it says: it teaches the agent to use the Membrane CLI to manage Rocket.Chat. Before installing or using it, verify you trust Membrane (getmembrane.com/@membranehq) because the integration proxies API calls through their service and they will see messages and metadata you send. If you have strict data-locality or compliance requirements, prefer a direct connector or a self-hosted solution. When following the SKILL.md: (1) confirm the npm package name and publisher (@membranehq/cli) before global installation, (2) review Membrane's privacy/security docs and the connector's permissions, and (3) avoid sharing secrets outside approved flows — the skill uses a browser OAuth-like login rather than requiring API keys, which is appropriate but still hands access to a third party.Like a lobster shell, security has layers — review code before you run it.
latestvk97csskznttd4h9mn84vte56q5842qns
License
MIT-0
Free to use, modify, and redistribute. No attribution required.