Overseerr

Request movies/TV and monitor request status via the Overseerr API (stable Overseerr, not the beta Seerr rewrite).

Security Scan

The skill's code, required environment variables, and runtime instructions are consistent with its stated purpose (interacting with an Overseerr API) and do not request unrelated credentials or contact unexpected endpoints.

Purpose & Capability

Name/description -> required binaries/env vars -> code all align: the scripts call only the Overseerr API (OVERSEERR_URL) and use the supplied OVERSEERR_API_KEY. No unrelated services, credentials, or OS-level resources are requested.

Instruction Scope

SKILL.md instructs running the provided Node scripts; the scripts only read the declared env vars, call the Overseerr API under /api/v1, and output JSON. The monitor script polls indefinitely and prints changes to stdout (expected behavior for a monitor). There are no instructions to read other files, credentials, or send data to external endpoints beyond OVERSEERR_URL.

Install Mechanism

No install spec; this is essentially an instruction+script bundle that requires the node binary. Nothing is downloaded from external URLs or written to arbitrary locations during install.

Credentials

Only OVERSEERR_URL and OVERSEERR_API_KEY are required (API key is declared as primary). This matches the API usage in the code and is proportionate; no extraneous SECRET/TOKEN/PASSWORD env vars are requested.

Persistence & Privilege

always is false and the skill does not modify other skills or system-wide settings. It can be invoked autonomously (platform default), which is expected for skills that make API calls — nothing here escalates privileges or requests permanent presence.

Assessment

This skill appears to do exactly what it claims: run Node scripts that communicate with your Overseerr instance using OVERSEERR_URL and OVERSEERR_API_KEY. Before installing: (1) only provide an API key that you trust — limit its privileges if possible; (2) run the scripts in an environment with a reasonably recent Node (fetch API used); (3) be aware the monitor script polls indefinitely and will make repeated requests to your Overseerr URL; (4) verify the skill source if you require provenance (the registry owner is listed but source is “unknown”). Otherwise the code looks straightforward and coherent with the described purpose.

Interact with a local/self-hosted Overseerr instance (search + request + status).

Note: This skill targets Overseerr (the current stable project), not the newer "Seerr" rewrite that is in beta.

Setup

Set env vars (recommended via your Clawdbot config):

• OVERSEERR_URL (example: http://localhost:5055)
• OVERSEERR_API_KEY (Settings → General → API Key)

Search

node {baseDir}/scripts/search.mjs "the matrix"
node {baseDir}/scripts/search.mjs "bluey" --type tv
node {baseDir}/scripts/search.mjs "dune" --limit 5

Request

# movie
node {baseDir}/scripts/request.mjs "Dune" --type movie

# tv (optionally all seasons, default)
node {baseDir}/scripts/request.mjs "Bluey" --type tv --seasons all

# request specific seasons
node {baseDir}/scripts/request.mjs "Severance" --type tv --seasons 1,2

# 4K request
node {baseDir}/scripts/request.mjs "Oppenheimer" --type movie --is4k

Status

node {baseDir}/scripts/requests.mjs --filter pending
node {baseDir}/scripts/requests.mjs --filter processing --limit 20
node {baseDir}/scripts/request-by-id.mjs 123

Monitor (polling)

node {baseDir}/scripts/monitor.mjs --interval 30 --filter pending

Notes:

• This skill uses X-Api-Key auth.
• Overseerr can also push updates via webhooks; polling is a simple baseline.