Mux
v1.0.2Mux integration. Manage Assets, Tracks, Metrics, Incidents. Use when the user wants to interact with Mux data.
⭐ 0· 241·1 current·1 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 name/description (Mux integration) matches the instructions: all runtime steps use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to the Mux API. No unrelated services, binaries, or credentials are requested.
Instruction Scope
SKILL.md stays within scope: it instructs installing and using the Membrane CLI, performing login flows, listing actions/connections, running actions, and using the Membrane proxy to call Mux endpoints. It does not ask the agent to read arbitrary local files, environment variables, or transmit data to unknown endpoints. Note: the proxy command allows arbitrary API calls to Mux under the connection's credentials, which is expected but worth being aware of.
Install Mechanism
This is an instruction-only skill (no install spec), but the README tells the user to run `npm install -g @membranehq/cli` (and uses `npx` elsewhere). Installing an npm package is a moderate-risk operation because it downloads and runs third-party code. That is reasonable for a CLI-based integration, but users should verify the package and prefer one-off `npx` or sandboxed installs if they are cautious.
Credentials
The skill declares no required env vars or credentials. It relies on Membrane to handle auth and credential refresh server-side, which aligns with the README advice not to ask users for API keys. Be aware that authenticating via Membrane means tokens/credentials are managed by Membrane's infrastructure and/or stored locally by the CLI per its own behavior.
Persistence & Privilege
The skill is not marked always:true and does not request elevated platform privileges. It does require the user to install a CLI that may store its own credentials locally, but the skill does not attempt to modify other skills or global agent settings.
Assessment
This skill appears coherent and uses the Membrane CLI to talk to Mux. Before installing or using it: 1) Verify the @membranehq/cli package and the getmembrane.com / GitHub repo are legitimate (inspect the package source if you can). 2) If uneasy, prefer one-off `npx` usage or install the CLI in a container/VM rather than system-wide. 3) Remember Membrane will handle and proxy your Mux credentials — only authenticate if you trust their service and review their privacy/security docs. 4) Be cautious when using the proxy feature (it can issue arbitrary API calls under your connection). 5) Avoid pasting unrelated secrets into conversation or into commands prompted by the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97344zb8fdg282tfjnc2kzkjd843zhp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.