Brightcove
v1.0.0Brightcove integration. Manage data, records, and automate workflows. Use when the user wants to interact with Brightcove data.
⭐ 0· 46·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
Name/description advertise a Brightcove integration and the SKILL.md consistently instructs the agent to use the Membrane CLI to connect, discover actions, run actions, and proxy requests to Brightcove. The actions and auth flow align with the stated purpose. Minor inconsistency: the skill metadata declares no required binaries, yet the runtime instructions require npm (to install the CLI) and the membrane CLI to be available.
Instruction Scope
SKILL.md stays within the scope of connecting to Brightcove via Membrane: it covers installing and using the Membrane CLI, login flow, creating connections, listing/running actions, and proxying API requests. It does not instruct reading unrelated files, requesting unrelated credentials, or sending data to unexpected endpoints. It does require browser-based auth (or headless flow) which is expected for this integration.
Install Mechanism
There is no formal install spec in the registry (instruction-only skill). The document tells users to run `npm install -g @membranehq/cli` or use `npx ...`, which is a typical but moderate-risk mechanism (pulls from npm at runtime). This is expected for a CLI-based integration, but users should verify the npm package and repository before installing and consider using npx or a local install to avoid global package installation.
Credentials
The skill requests no environment variables or credentials and explicitly delegates authentication to Membrane (server-side). That is proportionate to its stated purpose. The only external requirement is a Membrane account and network access, which the SKILL.md documents.
Persistence & Privilege
The skill is instruction-only, does not set always:true, and contains no code that would persist in the agent. It does not request persistent or system-wide privileges beyond running a CLI the user installs, so persistence and privilege level are appropriate.
Assessment
This skill is coherent: it uses Membrane's CLI to manage Brightcove via a standardized connector. Before installing, verify the @membranehq/cli npm package and its GitHub repo (to confirm you trust the publisher), prefer `npx` or a local install over global `-g` if you want to avoid modifying global packages, and be aware you'll perform a browser-based login that authorizes Membrane to access your Brightcove account (so only proceed if you trust Membrane to hold those credentials server-side). Also ask the skill author to declare required binaries (npm/node) in the skill metadata to remove the minor inconsistency.Like a lobster shell, security has layers — review code before you run it.
latestvk977qb482pnvqgvvdh9g1rpd6s84f2rh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.