Veritone
v1.0.2Veritone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Veritone data.
⭐ 0· 92·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
high confidencePurpose & Capability
The name/description say 'Veritone integration' and all runtime instructions explain how to use the Membrane CLI to authenticate and talk to Veritone; requiring a Membrane account and CLI is consistent with that purpose.
Instruction Scope
Instructions focus on installing and using the Membrane CLI, creating a connection, discovering actions, running actions, and proxying API requests. This stays within the stated purpose, but the proxy behavior means Membrane's servers will see requests and credentials—users should be aware their Veritone data/requests flow through Membrane.
Install Mechanism
There is no registry install spec; the SKILL.md tells users to run `npm install -g @membranehq/cli` (and uses npx in examples). Installing an npm CLI is expected here but carries the usual npm-package risk (arbitrary code execution at install time). Verify package provenance before global install.
Credentials
The skill declares no required env vars or credentials and instructs using browser-based login and Membrane-managed connections. This is proportionate; no unrelated secrets are requested. Note that credentials are managed server-side by Membrane rather than stored locally by the skill.
Persistence & Privilege
The skill is not always-enabled and makes no unusual persistence demands. The only persistent effect is normal CLI login/session storage and server-side connections managed by Membrane, which is expected for this integration.
Assessment
This is an instructions-only skill that tells you to install and use the Membrane CLI to proxy requests to Veritone. Before installing or using it: (1) confirm @membranehq/cli on npm is the legitimate publisher and review the package/repo; (2) understand that requests and auth will be handled by Membrane's servers (they will see the proxied data and tokens); (3) prefer running install commands in a controlled environment (or use npx) if you avoid global npm installs; (4) do not enter your Veritone API keys into the skill — follow the connection/browser auth flow as described; and (5) verify the getmembrane.com and the referenced GitHub repository are trustworthy for your data-sensitivity needs.Like a lobster shell, security has layers — review code before you run it.
latestvk97dc7xactyrqy2yh81qhv3zvn842te5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.