Uberduck
v1.0.0Uberduck integration. Manage data, records, and automate workflows. Use when the user wants to interact with Uberduck data.
⭐ 0· 56·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
Name and description match the runtime instructions: the SKILL.md tells the agent to use the Membrane CLI to connect to Uberduck and run actions or proxied requests. No unrelated services, binaries, or secrets are requested.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, logging in, creating a connector to Uberduck, listing and running actions, and optionally proxying raw API calls through Membrane. They do not direct the agent to read system files, harvest unrelated environment variables, or exfiltrate data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no install spec in registry), but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Global npm installs modify the host environment and fetch code from npmjs; this is expected for a CLI-driven integration but worth noting because it writes to disk and runs network installation at install time.
Credentials
The skill declares no required env vars or credentials. It explicitly recommends using Membrane connections (which handle auth server-side) rather than asking the user for raw API keys, so the requested privileges are minimal and proportional to the described functionality.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide changes or modify other skills' configurations. It relies on the Membrane CLI and the user's Membrane account for auth/session persistence, which is within scope.
Assessment
This skill is coherent and uses Membrane as a proxy to talk to Uberduck rather than asking you for Uberduck API keys. Before installing: (1) Review and trust the Membrane CLI (npm package @membranehq/cli) because the instructions ask you to install it globally; (2) Understand that using the connector and proxy means Membrane (the service) will see requests and data you send to Uberduck — check Membrane's privacy/security docs and OAuth scopes during login; (3) Be aware of legal/ethical concerns around voice cloning content; (4) Prefer using a dedicated account or scoped connection if you plan to use sensitive data. If you want, provide the Membrane connector ID or sample action you plan to run and I can help review the exact API call and required permissions.Like a lobster shell, security has layers — review code before you run it.
latestvk97d3abtp5ps09ghem0j6n84dd84bcv3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.