Userflow 1
v1.0.0Userflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Userflow data.
⭐ 0· 51·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
The name/description say 'Userflow integration' and the SKILL.md exclusively documents using the Membrane CLI to connect to Userflow, list actions, run them, and proxy raw API requests. Required capabilities (network access and a Membrane account) match the stated purpose; no unrelated credentials, binaries, or paths are requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI (login, connect, action list/run, and proxy requests). They do not instruct reading arbitrary files or environment variables. Note: network requests are proxied through Membrane (getmembrane.com), so request/response data and authentication flows will transit Membrane's service — this is expected for a proxy-based integration but is relevant for privacy/trust decisions.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to install @membranehq/cli globally via npm (npm install -g). That's a normal developer step for CLI-based integrations, but global npm installs carry the usual supply-chain risks (verify package provenance and prefer npx or isolated environments if concerned).
Credentials
The skill requires no environment variables or local secrets; it relies on Membrane to manage credentials server-side. The lack of requested local secrets aligns with the guidance in SKILL.md to let Membrane handle auth.
Persistence & Privilege
Flags are the platform defaults (always:false, agent-invocable true). The skill does not request permanent presence, nor does it instruct modifying other skills or global agent configuration.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to access Userflow. Before installing/using it, consider: (1) you must install @membranehq/cli (global npm installs modify your system—use npx or a container/venv if you prefer); (2) Membrane (getmembrane.com) will see proxied API requests and manage your Userflow credentials—verify you trust their service and review their privacy/security docs; (3) verify the @membranehq/cli package on npm/GitHub to ensure you are installing the expected project; (4) avoid sending highly sensitive data through the proxy unless you are comfortable with Membrane handling it; and (5) in headless or automated environments, follow the documented login flow and keep auth steps interactive or otherwise secured. Overall the skill is internally coherent, but standard supply-chain and privacy precautions for third-party CLI tooling apply.Like a lobster shell, security has layers — review code before you run it.
latestvk97946z4s9bsh8jsmfknj7k2as84cz07
License
MIT-0
Free to use, modify, and redistribute. No attribution required.