Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Chatfuel
v1.0.2Chatfuel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatfuel data.
⭐ 0· 104·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
The SKILL.md describes Chatfuel integration and all runtime instructions use the Membrane CLI (which proxies calls to Chatfuel). The skill does not request unrelated credentials or system access. One minor inconsistency: the package instructs installing a global npm CLI but the registry metadata lists no required binaries (e.g., node/npm), so the metadata is incomplete but not malicious.
Instruction Scope
Instructions are narrowly scoped to installing the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying requests. They do not direct the agent to read local files, harvest environment variables, or exfiltrate data to unexpected endpoints. The SKILL.md explicitly advises not to ask users for API keys and to let Membrane handle credentials.
Install Mechanism
Installation is via npm (npm install -g @membranehq/cli). That is a common, trackable mechanism (npm registry) but it does create a global binary on the system and requires node/npm be present. The install spec is not an arbitrary URL download, which reduces risk, but users should verify the npm package and its maintainers before installing globally.
Credentials
The skill declares no required environment variables or credentials and the instructions rely on OAuth/browser login via Membrane. There is no disproportionate request for unrelated secrets. Note: using Membrane means your Chatfuel credentials and auth tokens will be held/managed server-side by the Membrane service — this is expected but worth reviewing.
Persistence & Privilege
The skill is not forced-always, does not request system-wide config modifications, and does not ask to alter other skills. Autonomous invocation is allowed by default but that is the platform norm and not a red flag here.
Assessment
This skill appears coherent with its stated purpose, but before installing: 1) Verify the @membranehq/cli npm package and its maintainers (npmjs.com package page, repository code) and prefer inspecting source before global installation. 2) Be aware the CLI requires node/npm and will install a global binary; if you prefer less system-wide impact, consider installing it locally or in a sandbox. 3) Understand that Membrane will handle Chatfuel credentials server-side — review Membrane's privacy/security docs and trustworthiness before delegating your Chatfuel account access. 4) Confirm the homepage/repository links are legitimate (getmembrane.com, the GitHub repo) and match the npm package maintainers. 5) Note the skill metadata omitted required binaries (node/npm) — this is a documentation gap, not necessarily malicious.Like a lobster shell, security has layers — review code before you run it.
latestvk97b7kc99s043f12xpb9b69v7h842nvw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
