Leaseweb
v1.0.0Leaseweb integration. Manage data, records, and automate workflows. Use when the user wants to interact with Leaseweb data.
⭐ 0· 47·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 match the instructions: the skill tells the agent to use the Membrane CLI to manage Leaseweb resources. Nothing in the SKILL.md asks for unrelated credentials, binaries, or system access that would be out of scope for a cloud-provider integration.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating a connection, listing/running actions, and proxying requests to Leaseweb via Membrane. Important privacy/security note: all proxied API calls and credentials are handled by the Membrane service, so request payloads and resulting data will transit through Membrane's infrastructure — users should be aware that sensitive data will be visible to that third party.
Install Mechanism
There is no built-in installer; the SKILL.md tells the user to run `npm install -g @membranehq/cli`. This is a public npm package install (global) which is common for CLI tools but does modify the user's system PATH and requires npm privileges. Users should verify the package identity/source before installing.
Credentials
The skill declares no required environment variables, config paths, or credentials. The instructions explicitly say not to ask users for API keys and to rely on Membrane for auth — the requested access is minimal and proportional to the described purpose.
Persistence & Privilege
The skill is not forced-always, does not request persistent agent-wide privileges, and is user-invocable. There is no instruction to modify other skills or system-wide agent settings.
Assessment
This skill is coherent and appears to do what it says: use Membrane to access Leaseweb. Before installing or using it, confirm you trust the Membrane service and the `@membranehq/cli` npm package (check npmjs.org and the project's repo), because API calls and possibly sensitive request/response data will pass through Membrane. Prefer running the CLI in a controlled environment, avoid copying secrets into chat prompts, and verify Leaseweb resources and permissions after connecting. If you cannot or do not want a third party to proxy your Leaseweb traffic, do not use this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk977yq4cxd7rzc1qsfqjjzqxsh84fg11
License
MIT-0
Free to use, modify, and redistribute. No attribution required.