Webinarkit
v1.0.2WebinarKit integration. Manage data, records, and automate workflows. Use when the user wants to interact with WebinarKit data.
⭐ 0· 72·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.md describes using the Membrane CLI to manage WebinarKit resources, which matches the skill name/description. Minor inconsistency: the registry metadata lists no required binaries, but the runtime instructions instruct the user to install a global npm package (@membranehq/cli), so the skill implicitly requires npm/node to be available or installed.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, creating a connection, listing/ running actions, and proxying requests to the WebinarKit API via Membrane. The skill does not instruct reading unrelated files or environment variables and explicitly advises not to ask users for raw API keys.
Install Mechanism
There is no formal install spec in the registry (instruction-only), and the SKILL.md recommends installing @membranehq/cli from the public npm registry. This is a standard third‑party install (moderate trust required); there are no obscure download URLs or archive extraction steps.
Credentials
The skill declares no required env vars or credentials and the instructions rely on Membrane to handle auth flows (browser-based OAuth). No unrelated secrets are requested.
Persistence & Privilege
always:false and normal autonomous invocation are used. Note that once a Membrane connection is created the agent (when allowed to invoke the skill) can run arbitrary proxied API calls and actions against the connected WebinarKit account — this is expected for an integration but is the primary capability to be mindful of.
Assessment
This skill is coherent: it uses the Membrane CLI to access WebinarKit and does not ask for unrelated credentials. Before installing, verify the @membranehq/cli package and the Membrane project (homepage/repo) are legitimate, and ensure you are comfortable installing a global npm package (node/npm required). When authenticating, use the browser OAuth flow and review any actions or proxied API calls before running them. If you do not want the agent to act autonomously on your WebinarKit account, keep the skill user-invocable only (don’t grant it unrestricted autonomous invocation).Like a lobster shell, security has layers — review code before you run it.
latestvk976cpmt5k1vxg0nfq9xt85f39842tt1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.