Uplisting
v1.0.2Uplisting integration. Manage data, records, and automate workflows. Use when the user wants to interact with Uplisting data.
⭐ 0· 100·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 skill is an instruction-only Uplisting integration that relies on the Membrane CLI/proxy. That matches the name/description. One minor incoherence: SKILL.md instructs installing the @membranehq/cli via npm (and uses npx), but the skill metadata did not declare a required binary (node/npm). Declaring npm/node would be expected.
Instruction Scope
The instructions focus on using the Membrane CLI to discover actions, create connections, run actions, and proxy requests to the Uplisting API. They do not instruct reading arbitrary local files or unrelated environment variables, and they explicitly advise against asking users for API keys (Membrane handles credentials).
Install Mechanism
There is no formal install spec (instruction-only), which is low risk. However the SKILL.md recommends a global npm install (npm install -g @membranehq/cli) and also uses npx. That means the environment must have npm/node and will modify the user's global npm packages if followed — verify the package source before installing.
Credentials
The skill requests no environment variables or secrets. It uses Membrane to manage Uplisting credentials server-side; this is proportionate. Consider that using Membrane delegates credentials and proxied request contents to Membrane's platform, so trust in that service is required.
Persistence & Privilege
The skill is not always-enabled and has no install-time persistence or system-wide modifications beyond the optional user-run CLI install. It does not request elevated or cross-skill privileges.
Assessment
This skill is coherent: it tells the agent to use the Membrane CLI to connect to Uplisting and does not ask for extra secrets. Before installing or following the instructions: (1) make sure you have Node/npm if you plan to install the CLI — the skill didn't declare that dependency; (2) verify the authenticity of the @membranehq/cli package/repository (install from the official source) because a global npm install modifies your environment; (3) understand that Membrane will broker and see requests and credentials for Uplisting (so only use it if you trust Membrane's service and privacy); (4) if you want tighter control, prefer creating connections from your own account and review what data is proxied through Membrane. If you want me to, I can list the exact CLI commands you should run step-by-step or help verify the npm package homepage/repo before you install.Like a lobster shell, security has layers — review code before you run it.
latestvk979pc1b5en3qd3c7997x66tks843ebx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.