Dacast
v1.0.2Dacast integration. Manage Videos, Playlists, Channels. Use when the user wants to interact with Dacast data.
⭐ 0· 87·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
medium confidencePurpose & Capability
The skill claims to integrate with Dacast and all runtime instructions use Membrane to connect, list, run actions, and proxy requests to the Dacast API — this matches the stated purpose.
Instruction Scope
SKILL.md limits actions to installing and using the Membrane CLI, creating/listing connections, running prebuilt actions, and proxying requests to Dacast. It does not instruct reading unrelated files or exfiltrating arbitrary local data.
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md instructs installing @membranehq/cli via npm -g. Installing a global npm package is a reasonable step for this integration, but it is a network install from the public npm registry (moderate risk) and the skill does not declare this requirement in metadata.
Credentials
The skill declares no required environment variables and advises using Membrane-managed connections (no local API keys). This is proportionate: auth is handled by Membrane and the skill does not request unrelated secrets.
Persistence & Privilege
The skill is not always-on and allows normal autonomous invocation. Be aware that once authorized, Membrane connections can proxy arbitrary API requests to Dacast — expected for this integration but worth noting as it grants the skill access to whatever Dacast data the connection permits.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to manage Dacast resources and avoids asking for direct API keys. Before installing, confirm you trust the @membranehq/cli package and the Membrane service (check publisher, repository, and package integrity), since the SKILL.md tells you to run a global npm install (network download). Understand that you'll authenticate via your browser and grant Membrane access to your Dacast account — once authorized the connector can run arbitrary proxied requests to Dacast on your behalf. If you need stronger isolation, install and test the CLI in a sandbox or VM, verify the Membrane account permissions, and review the upstream repository (https://github.com/membranedev/application-skills) and getmembrane.com for legitimacy before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97f9nt0dyfzn39f492vmgnh9s843am1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.