Media Cli

v1.0.4

Single-file bash CLI for the *arr media stack with SSH remote support. For agents running on a different machine than the media services (e.g., VPS agent man...

0· 99·0 current·0 all-time
bySolomon Neas@solomonneas
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description describe a single-file bash CLI for *arr services and the SKILL.md only references bash, curl, python3, and ssh — all appropriate and expected for this purpose.
Instruction Scope
Runtime instructions tell the agent to clone the GitHub repo and run the install/setup wizard which stores API URLs/keys at ~/.config/media-cli/config; this is within scope but requires the agent to run shell commands and to use existing SSH config/keys. The SKILL.md does not instruct reading unrelated files, but you should review the install script before executing it.
Install Mechanism
This is an instruction-only skill with no install spec; install is expected to be a git clone and running the repo's install.sh on the user's machine. No arbitrary download URLs or archive extraction are included in the skill metadata.
Credentials
No environment variables, secrets, or config paths are declared beyond the config file (~/.config/media-cli/config) that the tool itself uses to store API keys. Required binaries listed in the docs match the described functionality.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It does not modify other skills or system-wide agent settings per the provided instructions.
Assessment
This skill appears coherent for managing a remote *arr stack, but take these precautions before installing: 1) Manually review the repository and the install.sh / media script you clone (don’t run without inspection). 2) Be aware the tool uses your SSH config/keys to tunnel API calls to the remote host — granting the agent the ability to run these commands effectively gives it SSH-based access to that host. 3) Confirm you trust the GitHub source (https://github.com/solomonneas/media-cli). 4) Keep the stored config (~/.config/media-cli/config) protected (chmod 600 is recommended) and only supply API keys for services you expect the tool to manage.

Like a lobster shell, security has layers — review code before you run it.

latestvk977fqyy696ajnb260qxekv0z183aq33

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments