Waratek
v1.0.0Waratek integration. Manage data, records, and automate workflows. Use when the user wants to interact with Waratek data.
⭐ 0· 33·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 name/description (Waratek integration) matches the instructions: the SKILL.md explains using the Membrane CLI to connect to Waratek, discover actions, run them, and proxy API requests. Required network access and a Membrane account are coherent with that purpose.
Instruction Scope
Instructions stay within the integration scope (install CLI, login via browser, create connections, list and run actions, and proxy API calls). Minor scope note: the document tells the user to install and run a third-party CLI and to perform interactive login flows; it does not instruct reading unrelated system files or exfiltrating secrets. The CLI's ability to proxy arbitrary API requests means Membrane will see request/response payloads — this is expected but worth understanding before use.
Install Mechanism
There is no formal install spec in the skill bundle, but SKILL.md instructs installing @membranehq/cli via npm -g. Installing a global npm CLI from the public registry is a standard distribution method but does introduce the normal risks of installing third-party packages globally (supply-chain / privilege on the host).
Credentials
The skill declares no required environment variables or local credentials. It explicitly recommends letting Membrane handle credentials and not asking the user for API keys, which is proportionate for a connector-based integration.
Persistence & Privilege
The skill does not request always-on presence and uses normal agent invocation. It does require the user to log in with Membrane (creates remote session/connection) but does not instruct modifying other skills or system-wide agent settings.
Assessment
This skill is internally consistent: it uses Membrane as a proxy/connector to Waratek and requires installing the @membranehq/cli and logging in via browser. Before installing, verify the @membranehq/cli package and the Membrane service are from a trusted vendor (check the npm package page and the GitHub repo), consider using npx or a local install instead of npm -g to avoid global installation, and be aware that Membrane will see proxied API requests and handle authentication server-side. If you have sensitive data or strict compliance requirements, use an account with minimal privileges and test the CLI in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk9741rwttqn1zzq686dkfw8n8d848ns0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.