Dux Soup
v1.0.0Dux Soup integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dux Soup data.
⭐ 0· 53·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/description (Dux Soup integration) aligns with the instructions: all actions use the Membrane CLI to connect to Dux Soup, discover actions, run them, or proxy API requests. No unrelated services, env vars, or binaries are requested.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, performing OAuth-style login, creating connections, listing and running actions, and proxying requests to the Dux Soup API via Membrane. It does not instruct reading unrelated files, environment variables, or sending data to unexpected external endpoints beyond Membrane.
Install Mechanism
There is no formal install spec, but the doc recommends installing @membranehq/cli globally with npm. Installing a third‑party global npm CLI is a normal requirement for this purpose but does carry the usual supply‑chain risk—verify the package and publisher (@membranehq) before running npm install -g.
Credentials
The skill declares no required env vars or credentials. It relies on Membrane to handle auth. This is proportionate, though note that Membrane (the service and its CLI) will manage and/or store the authenticated session and will proxy requests, meaning Membrane will see any data passed through it.
Persistence & Privilege
Skill is instruction-only, always:false, and does not ask to modify other skills or system-wide settings. Installing the recommended CLI will create local binaries and the CLI will persist login state (normal for a CLI). Nothing requests elevated or permanent agent privileges.
Assessment
This skill appears coherent and uses the Membrane CLI as its explicit runtime dependency. Before installing: 1) Verify the @membranehq npm package and publisher (review the package page, GitHub repo, and recent releases). 2) Understand that Membrane (the service) will proxy requests and thus will have access to any Dux Soup data you operate on—review Membrane's privacy/security docs and trust model. 3) Installing the CLI globally modifies your system (adds a binary and persists login tokens locally), so install only on machines you control. 4) For sensitive environments, consider using a scoped or containerized environment to limit where the CLI runs. 5) If you need more assurance, inspect the Membrane CLI source code and the referenced repository (github.com/membranedev/application-skills) before use.Like a lobster shell, security has layers — review code before you run it.
latestvk979vk5hyj2zzc5d1wqtfmy9b9848hpy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.