Formaloo
v1.0.2Formaloo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Formaloo data.
⭐ 0· 94·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 skill's name/description match the instructions: it uses Membrane as a proxy to interact with Formaloo. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in via browser, creating connections, listing actions, running actions, and proxying API requests. There are no steps that read local files, harvest unrelated env vars, or transmit data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no automatic install). It directs users to install @membranehq/cli from the public npm registry (npm install -g or npx). That is expected for the stated workflow but has the usual npm risks (you run third-party code when installing globally).
Credentials
No environment variables or local credentials are requested. The design delegates Formaloo credentials to Membrane (server-side). This is proportionate to the skill but requires trust in the Membrane service to hold and handle your Formaloo credentials.
Persistence & Privilege
The skill does not request permanent/always-on inclusion, does not modify other skills, and has no OS or config-path requirements. Autonomous invocation is allowed by default but is not combined with other concerning privileges.
Assessment
This skill is internally consistent but take these practical precautions before using it: (1) verify the @membranehq/cli package on npm and the linked GitHub repo to confirm authenticity; prefer npx or a non-global install if you want to avoid adding a global binary; (2) understand that using the skill requires a Membrane account and browser-based login — Membrane will hold and refresh Formaloo credentials on your behalf, so review their privacy/security documentation and permissions; (3) avoid running the global npm install in sensitive or locked-down environments without review; (4) if you need limited access, create a dedicated Formaloo/Membrane account or scoped connection rather than using high-privilege credentials. Overall the skill appears coherent for its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97fscen6pvjqx31d42d6bg8p58433h6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.