Jw Player
v1.0.2JW Player integration. Manage Medias, Playlists, Players. Use when the user wants to interact with JW Player data.
⭐ 0· 90·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 match the runtime instructions: the SKILL.md shows using Membrane to connect to JW Player, list/run actions, and proxy requests. No unrelated credentials, binaries, or paths are requested.
Instruction Scope
Instructions are narrow: install Membrane CLI, run membrane login/connect/action/request commands, and use Membrane's proxy. They do not ask the agent to read arbitrary files, environment variables, or transmit data to unexpected endpoints beyond Membrane/JW Player.
Install Mechanism
This is an instruction-only skill (no install spec), but it recommends installing @membranehq/cli via npm (-g). Using npm is a common pattern but carries the usual supply-chain considerations — the recommendation is traceable to a public package rather than an arbitrary download.
Credentials
The skill declares no required env vars or credentials and explicitly instructs that Membrane handles auth server-side. It does not request unrelated secrets or environment access.
Persistence & Privilege
The skill is not forced-always and is user-invocable. It has no install artifacts or config changes in the skill bundle, and does not request elevated or persistent system presence.
Assessment
This skill is internally consistent and delegates JW Player access to the Membrane service. Before using it: (1) verify you trust Membrane — the skill requires a Membrane account and installing @membranehq/cli via npm; (2) inspect / confirm the npm package and its maintainers (supply-chain risk of global npm installs); (3) when creating the connector, review the permissions/scopes requested by the JW Player connection and limit to only what you need; (4) in sensitive or corporate environments, consult your security/compliance team before adding third-party connectors or installing global CLIs. If you need higher assurance, ask the skill author for a repository or published package link and for details on what Membrane stores/retains for connections.Like a lobster shell, security has layers — review code before you run it.
latestvk97b5v4fdzphkkjx6cwyah96c9842s38
License
MIT-0
Free to use, modify, and redistribute. No attribution required.