Cloud Elements
v1.0.0Cloud Elements integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloud Elements data.
⭐ 0· 44·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
Name/description (Cloud Elements integration) match the runtime instructions: the SKILL.md consistently instructs the agent to use the Membrane CLI to discover, connect to, and proxy requests to Cloud Elements. No unrelated services, env vars, or capabilities are requested.
Instruction Scope
Instructions stay on-topic: install and use the Membrane CLI, create connections, list actions, run actions, and proxy requests. The doc does not instruct reading unrelated files, scanning system config, or exfiltrating data outside the described flow. It does require network access and a Membrane account (declared in the SKILL.md).
Install Mechanism
There is no registry install spec, but the SKILL.md tells users to run `npm install -g @membranehq/cli` (and recommends `npx` in places). Installing an npm package globally is common for CLIs but carries the usual supply-chain risk of running third‑party install scripts. This is a proportionate mechanism for a CLI integration but worth verifying the package and its publisher before installing.
Credentials
The skill declares no required environment variables and the instructions explicitly advise not to ask users for API keys. Authentication is handled by Membrane via browser auth flows and server-side token management, which is consistent with the stated purpose. The only credentials in play are the user's Membrane account/connection to Cloud Elements (expected).
Persistence & Privilege
The skill is instruction-only, has no 'always: true', and does not request persistent system-wide configuration. Autonomous invocation is allowed by default (disable-model-invocation: false) — normal for skills — and does not by itself create extra risk here.
Assessment
This skill is coherent but depends on trusting Membrane/@membranehq and installing their CLI. Before installing or granting a connection: 1) verify the Membrane homepage and npm package reputation; inspect the package (or prefer using npx to avoid a global install). 2) Understand that when you complete the browser auth, Membrane will hold credentials and can act on your Cloud Elements account — only grant the minimal needed permissions and use ephemeral or limited-scope connections where possible. 3) In headless or CI environments you will need to follow the printed URL/code flow manually. 4) If you want extra caution, review the @membranehq/cli package source on GitHub and the privacy/security docs for Membrane before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97aktkkkp6q8zq0ywcqawczn584ffx7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.