← Back to Skills Marketplace
ymgenc

Plex Media Remote

by Yahya · GitHub ↗ · v1.1.0 · MIT-0
cross-platform ⚠ suspicious
117
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install plex-control
Description
A standalone command-line skill to interact with and manage Plex Media Server directly, featuring playback controls and secured temporary caching.
Usage Guidance
This skill appears to implement a legitimate Plex CLI and only needs your Plex URL and token to function, but there are a few concerns to check before installing: - Confirm the source: the package has no homepage and comes from an unknown owner. If you don't trust the author, don't install. - Resolve the metadata mismatch: the top-level registry summary lists no required env vars/binaries, but SKILL.md and metadata.json require PLEX_URL, PLEX_TOKEN, 'uv', and 'python3'. Make sure you (or the platform) provide these correctly; otherwise the agent may fail or attempt unexpected actions. - 'uv' is an uncommon runner; ensure you know what 'uv' will do on your system or provide an alternate invocation (python3 scripts/plex_cli.py) if you prefer. - Treat PLEX_TOKEN as a sensitive secret. Only provide it if you trust the skill and the environment where it's run. - Consider privacy: the skill returns live session info (usernames, player addresses) to stdout and caches media titles/actors/genres in the system temp directory. If that is acceptable for your environment, proceed; otherwise do not install. If you want higher assurance, ask the publisher for a known homepage or repo, or run the included script locally in a controlled environment first to verify behavior.
Capability Analysis
Type: OpenClaw Skill Name: plex-control Version: 1.1.0 The Plex Standalone Skill is a legitimate tool for managing a Plex Media Server. It uses the standard 'plexapi' library and handles sensitive credentials (PLEX_TOKEN) via environment variables as expected for OpenClaw agents. The caching mechanism in 'scripts/plex_cli.py' uses the system's temporary directory to store non-sensitive media metadata for performance, and no evidence of data exfiltration, malicious execution, or prompt injection was found.
Capability Assessment
Purpose & Capability
The script and SKILL.md claim the skill requires PLEX_URL and PLEX_TOKEN and the binaries 'uv' and 'python3' (and the Python dependency plexapi). Those requirements are coherent with a Plex-control CLI. However, the registry-level info provided at the top of the package (the 'Requirements' summary) lists no required env vars or binaries — a direct inconsistency between how the skill advertises itself at the package level and the internal metadata.json / SKILL.md. This mismatch is unexplained and could cause confusion or accidental failure when installing or running the skill.
Instruction Scope
The SKILL.md instructs the agent to run the included script via 'uv run scripts/plex_cli.py' and to inject PLEX_URL and PLEX_TOKEN into the environment. The script only contacts the specified Plex server and writes a JSON cache to the OS temp dir; it does not attempt to read local dotfiles or other system credentials. It does, however, fetch and return potentially sensitive live session data (usernames, playback state, client addresses) to stdout — this is expected for a Plex management tool but is privacy-sensitive and should be considered by the user.
Install Mechanism
There is no formal install spec (instruction-only), which is low risk, but the SKILL.md and metadata.json expect dependencies to be handled automatically via the 'uv' runner. 'uv' is an uncommon runtime tool and is listed as a required binary inside metadata.json but was not declared in the top-level package requirements. Because there is no explicit, reproducible install step, running the skill may fail or cause the agent to try to install/run tools it doesn't have. No network download URLs or extract/install steps are present.
Credentials
The only sensitive environment variables accessed are PLEX_URL and PLEX_TOKEN, which are proportionate and necessary for connecting to a Plex server. The script reads only those env vars. The problem is that the top-level provided manifest initially listed no required env vars while internal files require them — a packaging inconsistency the user should resolve before granting credentials.
Persistence & Privilege
The skill does not request permanent or privileged presence: 'always' is false, it does not modify other skills or system-wide settings, and it writes only a transient cache to the OS temp directory. It does not persist tokens to disk. No elevated privileges or persistent agent modifications are requested.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install plex-control
  3. After installation, invoke the skill by name or use /plex-control
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
- Added formal registry metadata file (metadata.json) specifying environment variables and binary dependencies. - Updated documentation to clarify configuration, security, and cache behavior. - Now declares requirements (environment variables, binaries) explicitly in metadata. - Emphasized that only non-sensitive library metadata is cached, and session/playback info is never stored. - No code changes to functionality; this is a documentation and metadata update.
v1.0.1
Suspicious flag misunderstanding correction
v1.0.0
Initial standalone CLI skill release for Plex: - Added standalone Python CLI (`scripts/plex_cli.py`) to interact with Plex Media Server directly. - Introduced local media cache (`media_cache.json`) for instant, offline search functionality. - Provided commands for server info, libraries, searching media, viewing sessions, on-deck content, and playback controls (play, pause, resume, stop) on specified clients. - Streamlined usage instructions and requirements in updated documentation; no MCP server required. - All script actions respond with structured JSON output for easy parsing.
Metadata
Slug plex-control
Version 1.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Plex Media Remote?

A standalone command-line skill to interact with and manage Plex Media Server directly, featuring playback controls and secured temporary caching. It is an AI Agent Skill for Claude Code / OpenClaw, with 117 downloads so far.

How do I install Plex Media Remote?

Run "/install plex-control" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Plex Media Remote free?

Yes, Plex Media Remote is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Plex Media Remote support?

Plex Media Remote is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Plex Media Remote?

It is built and maintained by Yahya (@ymgenc); the current version is v1.1.0.

💬 Comments