Wbiztool
v1.0.0Wbiztool integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wbiztool data.
⭐ 0· 91·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
Name/description say 'Wbiztool integration' and the SKILL.md only instructs the agent to use the Membrane CLI to discover/run Wbiztool actions and proxy API requests. Required capabilities (network access and a Membrane account) match the described purpose.
Instruction Scope
The SKILL.md stays on-topic: it instructs installing and using the Membrane CLI, logging in, creating/listing connections, listing and running actions, and proxying requests. It does not ask the agent to read unrelated files, access unrelated env vars or exfiltrate arbitrary data.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the README tells the user to run 'npm install -g @membranehq/cli'. Installing a global npm package runs third-party code on the host and requires trusting that package and its registry distribution. This is expected for a CLI-based integration, but it is an external trust/deployment decision the user should consider.
Credentials
The skill declares no required env vars or credentials. The SKILL.md explicitly tells users not to provide API keys and instead create a connection through Membrane, which centralizes auth server-side. The requested privileges are proportional to the described integration.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide persistence or modification of other skills. It relies on the Membrane CLI and the user's browser-based authentication flow; autonomous invocation is allowed by platform default but not combined with other red flags.
Assessment
This skill appears internally consistent: it uses the Membrane CLI as a legitimate proxy to talk to Wbiztool and does not request unrelated secrets. Before installing, consider: (1) you must install and trust the @membranehq/cli npm package — installing global npm packages executes third-party code on your machine; review the package and its source repository, and prefer pinned versions or use an isolated environment (container/VM) if you want to limit risk; (2) the skill depends on the Membrane service and browser-based auth, so review Membrane's privacy/security docs and verify the homepage/repo match the published package; (3) the skill does not ask for API keys locally — it delegates auth to Membrane — but that means the Membrane account/service will mediate access to your Wbiztool data; ensure you are comfortable with that trust boundary; (4) if you need higher assurance, manually inspect the @membranehq/cli package or run it in a sandbox before granting it access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk97e00pytjjtkc6wh08qnqr3v584hf0g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.