Weweb
v1.0.0WeWeb integration. Manage data, records, and automate workflows. Use when the user wants to interact with WeWeb data.
⭐ 0· 63·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's name and description (WeWeb integration) align with the instructions: it uses the Membrane CLI to connect to WeWeb, list actions, run actions, and proxy API requests. The homepage points to Membrane (the proxy service), which is consistent with the implementation.
Instruction Scope
SKILL.md instructs the agent/user to install and use the @membranehq/cli, run membrane login, list connections/actions, run actions, and proxy requests to WeWeb. All of these steps are within the stated purpose. However the document assumes availability of npm/node and network/browser access (for interactive login) but does not declare those requirements explicitly.
Install Mechanism
There is no formal install spec in the registry bundle; instead the instructions recommend installing a global npm package (npm install -g @membranehq/cli) or using npx. Installing from the public npm registry is a common pattern but will download and run third-party code on the host—this is expected for a CLI but should be considered when granting installation permission.
Credentials
The skill does not request environment variables, local config paths, or secret values. It requires a Membrane account and interactive browser-based authentication, which is proportionate to a proxy-based integration. There are no unexplained credential requests.
Persistence & Privilege
The skill is instruction-only and has no code files, no install spec in the registry, and does not request 'always' persistence. It does not attempt to modify other skills or system-wide settings.
Assessment
This skill is coherent: it uses Membrane as a proxy to talk to WeWeb and asks you to install the @membranehq/cli (npm). Before installing, confirm you trust the Membrane project and the npm package (review https://github.com/membranedev/application-skills and the @membranehq/cli package page). Note that installing the CLI will download third-party code and that Membrane will handle/see proxied requests to your WeWeb account (so review Membrane's privacy/security policy). Prefer using npx for ephemeral usage if you don't want a global install, and ensure a browser-capable auth flow is acceptable for your environment. Finally, because the skill can proxy arbitrary API calls to WeWeb via Membrane, be careful what data you allow it to access or send—only enable the skill if you are comfortable granting it that capability.Like a lobster shell, security has layers — review code before you run it.
latestvk970cp10fzs3a8tms5wdjvg0118499vp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.