Intercom Articles
v1.0.2Intercom Articles integration. Manage data, records, and automate workflows. Use when the user wants to interact with Intercom Articles data.
⭐ 0· 52·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
medium confidencePurpose & Capability
The name/description match the instructions: all actions are performed through the Membrane CLI and a Membrane connection to Intercom Articles. There are no unrelated env vars, binaries, or config paths requested.
Instruction Scope
SKILL.md stays on-scope (install CLI, login, create/choose a connection, run pre-built actions or proxy requests). It does instruct global npm installation and an interactive browser login (or headless token flow). It does not direct reading of unrelated local files or asking for local secrets.
Install Mechanism
There is no formal install spec in the registry, but the README tells users to run `npm install -g @membranehq/cli` (and sometimes `npx`). This is a public npm package install (moderate risk): it modifies the host environment and you should verify the package and its publisher before installing globally.
Credentials
The skill declares no env vars and explicitly says not to ask for API keys. However, it requires a Membrane account/connection: granting that connection performs auth on your behalf and can give Membrane access to your Intercom data. Make sure the connection's permissions are limited to what's needed.
Persistence & Privilege
always:false and no config paths or cross-skill modifications are requested. The skill being user-invocable and able to be invoked autonomously is the platform default and not itself suspicious here.
Assessment
This skill appears to do what it says — it relies on the Membrane CLI and your Membrane account to talk to Intercom. Before installing or using it: (1) verify @membranehq/cli on npm (publisher, version, and recent activity) rather than blindly running a global install; (2) review the connection permissions in Membrane and grant least privilege for Intercom; (3) avoid pasting API keys into prompts — use the connection flow; and (4) if installing on a shared or production machine, prefer a non-global or isolated install and inspect the package source (GitHub repo) first.Like a lobster shell, security has layers — review code before you run it.
latestvk970594ap52fp5m8tjvh6vxrb5842nfe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.