Videoask
v1.0.0VideoAsk integration. Manage data, records, and automate workflows. Use when the user wants to interact with VideoAsk data.
⭐ 0· 57·0 current·0 all-time
byMembrane Dev@membranedev
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 VideoAsk and all runtime instructions use the Membrane CLI to discover connections, run actions, and proxy API requests — this matches the stated purpose. Small inconsistency: the SKILL.md instructs installing/running the Membrane CLI via npm/npx, but the registry metadata did not declare any required binaries (node/npm) or installation steps. Also the skill references Membrane (getmembrane.com) rather than VideoAsk directly, which is reasonable because Membrane is acting as the integration layer, but you should be aware the skill depends on a third-party proxy service (Membrane).
Instruction Scope
The runtime instructions stick to using the Membrane CLI to authenticate, discover actions, run actions, and proxy requests to the VideoAsk API. They do not instruct reading arbitrary local files, unrelated environment variables, or sending data to unexpected endpoints. The flow includes interactive browser-based auth and a headless login option (user copies a URL/code) which is expected for OAuth-like flows.
Install Mechanism
There is no formal install spec in the registry, but SKILL.md recommends 'npm install -g @membranehq/cli' or using 'npx @membranehq/cli@latest'. Installing or running remote code from npm is common for CLIs but has moderate risk: npx/@latest executes code downloaded at runtime and global npm installs write to the host system. Verify the @membranehq/cli package and prefer a pinned version if you want reproducibility and auditability.
Credentials
The skill requests no environment variables or credentials in the registry and the instructions explicitly state that Membrane handles credentials server-side and that you should not ask users for API keys. This is proportionate: the service requires an account with Membrane and a browser-based auth flow, which aligns with the described functionality.
Persistence & Privilege
The skill does not demand always-on inclusion (always: false) and does not request system-wide config changes. The only persistent effect would be installing the Membrane CLI (global npm install), which modifies the host environment — expected for a CLI-based integration but worth noting since it alters system state.
Assessment
This skill appears to do what it says: it uses Membrane as a proxy to interact with VideoAsk and avoids asking for raw API keys. Before installing, confirm you trust the Membrane service and the @membranehq/cli npm package (check the GitHub repo, package publisher, and package versions). Prefer using npx with an explicit version or pin a specific CLI release rather than using '@latest' to reduce the chance of unexpected remote code execution. Be aware that a global npm install modifies your system (requires npm/node). Finally, review Membrane's privacy and data handling policies so you understand what data will be proxied through their servers.Like a lobster shell, security has layers — review code before you run it.
latestvk9740hsgnrv3bqnkxn6qfb8t0184cnv3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.