Wobaka
v1.0.2Wobaka integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wobaka data.
⭐ 0· 112·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 (Wobaka integration) aligns with the instructions (use Membrane CLI to discover connections, run actions, or proxy requests to Wobaka). Nothing in the SKILL.md asks for unrelated service credentials or resources.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in via browser, discovering connections, running actions, and proxying API calls. The instructions do not request reading local files, unrelated env vars, or sending data to unexpected endpoints.
Install Mechanism
There is no platform install spec in the registry (skill is instruction-only). The SKILL.md instructs the user to run `npm install -g @membranehq/cli` which is a common pattern for CLI tools but does modify the host environment (global npm install). This is expected for a CLI-based integration but users should verify the npm package source before installing.
Credentials
The skill declares no required env vars and the instructions explicitly advise against asking users for API keys, instead using Membrane-managed connections. No disproportionate credential access is requested.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system-wide privileges. It does not modify other skills or agent configuration in the instructions. Note: autonomous invocation is allowed by platform default, but that is not combined with broad credentials here.
Assessment
This skill is instruction-only and coherent: it uses the Membrane CLI to interact with Wobaka and does not ask for unrelated credentials. Before installing: (1) confirm the npm package @membranehq/cli is from a trusted source (check the package page and GitHub repo), (2) be aware `npm install -g` modifies your system PATH—install in a controlled environment if you prefer, (3) review the permissions granted when you create a Membrane connection (only connect accounts you trust), and (4) if you run agents that can invoke skills autonomously, ensure you understand what account the Membrane CLI will access so the agent can't act on data you don't want it to handle.Like a lobster shell, security has layers — review code before you run it.
latestvk971c1cv8yess6a4mg64ny8jrx842p5v
License
MIT-0
Free to use, modify, and redistribute. No attribution required.