Webinarjam
v1.0.2WebinarJam integration. Manage data, records, and automate workflows. Use when the user wants to interact with WebinarJam data.
⭐ 0· 78·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 WebinarJam and consistently delegates auth and API access to the Membrane CLI/proxy. No environment variables, unrelated binaries, or external services are requested that would be inconsistent with a WebinarJam integration.
Instruction Scope
SKILL.md contains concrete CLI steps (installing the Membrane CLI, logging in, creating/using a connection, running actions or proxied requests). It does not instruct reading unrelated files, harvest system secrets, or transmit data to unexpected endpoints beyond Membrane/WebinarJam.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing a global npm package (@membranehq/cli). Installing global npm packages is a common pattern but has moderate operational considerations (requires appropriate permissions and installs code on the machine). Suggest using npx or auditing the CLI package before global install if you prefer not to add software system-wide.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The documentation explicitly delegates credential handling to Membrane and advises against asking users for API keys, which is proportionate for this integration.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or agent-wide settings, and is user-invocable. It does not request persistent elevated privileges.
Assessment
This skill is coherent: it relies on the Membrane CLI to handle auth and proxy requests to WebinarJam. Before installing, verify the @membranehq/cli package and the Membrane service (homepage/repository) are the legitimate projects you expect. If you prefer not to install global npm packages, use npx for one-off runs. During the Membrane login/connect flows, review the OAuth consent and what access the connector requests; because credentials are managed server-side by Membrane, consider the privacy/security policies of Membrane before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97b88y2zfc6tg93sbaawydqes843a7a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.