Whatfix
v1.0.0Whatfix integration. Manage data, records, and automate workflows. Use when the user wants to interact with Whatfix data.
⭐ 0· 56·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 skill declares a Whatfix integration and the SKILL.md consistently instructs using the Membrane CLI to connect to Whatfix and run connector/action commands. Asking to install a CLI and to authenticate via Membrane is proportionate to the stated purpose.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, creating/searching connections, listing actions, and performing Whatfix-related operations. There are no instructions to read arbitrary local files, harvest unrelated environment variables, or send data to unexpected endpoints beyond the Membrane/Whatfix flows.
Install Mechanism
This is an instruction-only skill that tells users to run `npm install -g @membranehq/cli` (and later references `npx @membranehq/cli@latest`). Installing a global npm package is a reasonable install mechanism for a CLI, but it brings code onto the host. The instructions do not pin a specific package version and rely on an external registry, which is moderate risk compared with no install. If you care about reproducibility/auditability, review the CLI's source and prefer a pinned release.
Credentials
The skill declares no required env vars in registry metadata, but the SKILL.md states you need a Membrane account and network access; this implies you'll provide credentials to Membrane via the CLI auth flow (browser-based). That is expected for a third-party integration, but it means you must trust Membrane with access to your Whatfix account. No unrelated credentials are requested.
Persistence & Privilege
The skill is not flagged as always included and allows normal autonomous invocation (platform default). The main persistence impact is installing a global CLI binary (`membrane`) which modifies the system PATH; this is normal for a CLI but worth noting before installation.
Assessment
Before installing: understand that this skill delegates all network/auth work to the Membrane CLI. Installing it will add a global npm binary to your system and you will authenticate via Membrane (browser flow or headless code). Verify the trustworthiness of @membranehq/cli: review its GitHub repo and recent releases, prefer installing a pinned version rather than an unpinned `-g` latest, and, if possible, run the CLI in an isolated environment (container or VM) if you have sensitive Whatfix data. If you do not trust Membrane or cannot review its source, do not install or provide credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97ehv8nc4yvsjj48acsvyz7an84azg4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.