Uplead
v1.0.0UpLead integration. Manage data, records, and automate workflows. Use when the user wants to interact with UpLead data.
⭐ 0· 91·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 and description (UpLead integration) match the runtime instructions: the SKILL.md tells the agent to use the Membrane CLI to connect to UpLead, list actions, run actions, and proxy raw requests. Nothing requested (no env vars, no config paths) is inconsistent with this purpose.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying API calls. The skill does not instruct the agent to read local files, harvest unrelated environment variables, or exfiltrate data to third-party endpoints outside of Membrane/UpLead.
Install Mechanism
The SKILL.md recommends installing @membranehq/cli globally via npm. This is a common pattern but has moderate risk: installing a global npm package runs code on your machine and requires trust in the package/publisher. The registry itself contains no install spec (instruction-only), so installation is manual and not enforced by the skill.
Credentials
The skill declares no required environment variables or credentials, which is proportional. However, it relies on Membrane to perform authentication server-side — that means Membrane (and the @membranehq/cli you install) will handle and have access to UpLead credentials and proxied API calls. This is expected for a proxy-based integration but requires trusting the external service.
Persistence & Privilege
The skill does not request persistent presence (always:false) and does not instruct modifying other skills or system-wide settings. It does instruct the user to install a CLI, which is local installation but not an autonomous persistence flag.
Assessment
This skill is internally consistent for an UpLead integration that uses Membrane as a proxy, but before installing or using it you should: 1) Confirm you trust the Membrane service and the @membranehq/cli npm package (review the package on npm and its GitHub repo at the listed homepage/repository). 2) Avoid installing global npm packages on shared or production machines; prefer a contained environment (container or VM) if you are unsure. 3) Understand that Membrane will handle UpLead authentication and therefore will have access to your UpLead account and any proxied data — review Membrane's privacy/security docs and terms. 4) In headless setups, follow the documented login flow carefully and verify URLs before copying codes. If you need stronger assurance, inspect the CLI source code on GitHub (repository listed in SKILL.md) before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk977smye8g7mh816zcjkrph0qx84h4z3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.