Squadcast
v1.0.0Squadcast integration. Manage data, records, and automate workflows. Use when the user wants to interact with Squadcast data.
⭐ 0· 52·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
The skill claims to integrate with Squadcast and all runtime instructions use the Membrane CLI to discover actions, create connections, run actions, or proxy raw API requests. Requiring Membrane (a proxy/connector service) is coherent with the stated purpose.
Instruction Scope
SKILL.md instructs the agent to install and run membrane CLI commands, perform browser-based login flows, list and run connector actions, and proxy requests through Membrane. These actions stay within the described integration scope, but they route Squadcast requests via Membrane (a third-party service), which implies that request/credentials will be handled by Membrane rather than locally.
Install Mechanism
There is no packaged install spec in the registry; the doc tells users to install @membranehq/cli via npm (-g). Installing a global npm package is a common approach but does write to the host and may run package lifecycle scripts—standard risk for any global npm install. The source (npm) is a known registry.
Credentials
The skill declares no required env vars, no credentials, and no config paths. The instructions rely on Membrane to manage credentials and browser-based auth, which is proportionate to the stated behavior. The key privacy consideration is trusting Membrane with the Squadcast connection.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges, does not modify other skills' configs, and is user-invocable. It has no built-in persistence or privileges beyond normal CLI usage.
Assessment
This skill uses the Membrane CLI to access Squadcast and asks you to install a global npm package and perform a browser-based login. It does not request local secrets or system-wide privileges, but you should: (1) understand that you are granting Membrane a Squadcast connection (review Membrane's privacy, security, and OAuth scopes before connecting); (2) verify the npm package (@membranehq/cli) and its publisher on the npm registry before installing; and (3) be aware that global npm installs run package scripts (a normal risk). If you prefer not to hand integration access to a third party, consider using Squadcast's official API or an alternative connector you trust.Like a lobster shell, security has layers — review code before you run it.
latestvk9776bdrzmz0bapm0mwyqr8yen84ecjh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.