Upcloud
v1.0.0UpCloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with UpCloud data.
⭐ 0· 28·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
The name and description promise an UpCloud integration and every instruction uses the Membrane CLI to create connections, list actions, run actions, or proxy requests to UpCloud. There are no unrelated required env vars, binaries, or config paths.
Instruction Scope
The SKILL.md stays on-topic: it instructs installing/using the Membrane CLI, logging in, creating a connector, running actions, and proxying raw API requests. It does not direct the agent to read local files or environment variables. Note: the proxy command allows arbitrary HTTP calls to the UpCloud API via Membrane — this is expected for an integration but means the agent (or user) can send arbitrary requests once a connection exists.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the doc tells users to run 'npm install -g @membranehq/cli' or use 'npx'. Installing a global npm package executes code from the npm registry; that is a normal way to install a CLI but you should verify the package/source before installing. The instructions themselves do not download code from obscure URLs.
Credentials
The skill declares no required environment variables or credentials and tells users to create a Membrane connection for UpCloud. This is proportionate: Membrane is used to hold credentials server-side, so the skill does not request unrelated secrets.
Persistence & Privilege
always is false and there are no requests to modify other skills or system-wide configs. The skill is user-invocable and may be called autonomously by the agent (platform default), which is normal for skills of this type.
Assessment
This skill appears coherent, but review a few practical items before using it: (1) It delegates auth to Membrane — granting a Membrane connector access to your UpCloud account gives Membrane (and any code running under its authority) the ability to act on that account; review connector scopes and Membrane's privacy/security docs. (2) The docs recommend installing an npm CLI globally; prefer using 'npx' or inspect the @membranehq/cli package on the npm registry/GitHub before installing. (3) The 'membrane request' proxy can send arbitrary API calls to UpCloud — only perform actions you trust and avoid pasting sensitive keys into chat. (4) The skill source is listed as unknown; if provenance matters, verify the repository/package publisher before use. (5) If you allow autonomous agent invocation, be aware the agent could use the Membrane connection to perform actions without additional prompts; keep that in mind when granting permissions.Like a lobster shell, security has layers — review code before you run it.
latestvk97483688tqvq52m78sn274ajs8489q2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.