Radarr+
Analysis
Radarr+ mostly matches its movie-request purpose, but one documented helper can execute scripts from a hard-coded developer workspace path, so it deserves review before installation.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
return _run_json(["bash", "-lc", "cd /home/vishix/.openclaw/workspace && ./skills/radarr/scripts/radarr.sh " + " ".join(args)])
A helper that is referenced by the documented workflow shells into a hard-coded developer workspace rather than using the installed package-relative script path, so it may execute a different/unreviewed copy of the skill or fail unexpectedly.
created = _request("/api/v3/movie", method="POST", body=movie)
...
body={"name": "MoviesSearch", "movieIds": [created["id"]]}The helper can add movies to Radarr and trigger a Radarr search command, which is exactly the skill's purpose but is still a mutating action.
A periodic dispatcher should run: `./skills/radarr/scripts/poll_and_queue.py` ... create outbox items under `./state/radarr/outbox/`
The skill supports ongoing polling and queued notifications after the initial request; this persistence is disclosed and tied to progress updates.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Set secrets in `~/.openclaw/.env` ... `RADARR_API_KEY=...` ... `PLEX_TOKEN=...`
The skill requires a Radarr API key and optionally uses a Plex token; these credentials are expected for the integration and the artifacts do not show hardcoded secrets or credential logging.
