Demio
v1.0.2Demio integration. Manage Webinars, Registrations. Use when the user wants to interact with Demio data.
⭐ 0· 122·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 name/description (Demio integration) match the content: instructions show how to use the Membrane CLI to connect to Demio, list actions, run actions, and proxy raw API requests. Nothing requested (no env vars, no unrelated binaries) is out of scope.
Instruction Scope
SKILL.md only instructs use of the Membrane CLI, browser-based login flow, and Membrane proxy to Demio endpoints. It does not instruct reading unrelated files, environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
No automated install spec in the registry (instruction-only). The docs tell users to run `npm install -g @membranehq/cli` — an expected distribution method but one that installs a global npm package (runs third-party code). Verify the package is the official @membranehq/cli before installing in production or shared systems.
Credentials
The skill declares no required environment variables or credentials and explicitly advises letting Membrane handle auth rather than asking users for API keys. It does require a Membrane account (server-side credential handling), which is proportional to the integration.
Persistence & Privilege
The skill is instruction-only, does not request persistent presence (always:false), and does not ask to modify other skills or system-wide settings.
Assessment
This skill appears coherent and benign, but before using it: (1) Confirm @membranehq/cli is the official package (npm scoped packages can run arbitrary code when installed globally). (2) Be aware authentication is handled by Membrane — your Demio credentials are managed server-side by Membrane, so only proceed if you trust that service and its privacy/security posture. (3) In shared or CI/headless environments, follow the documented headless login flow carefully to avoid exposing auth codes. (4) If you need stricter controls, consider creating a limited Demio account/connection with least privilege and monitor activity on your Membrane/Demio accounts.Like a lobster shell, security has layers — review code before you run it.
latestvk97dm3y0k0xsfk8mwcfvsv0ga1842xxr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.