Radarr+
PassAudited by ClawScan on May 10, 2026.
Overview
Radarr+ appears to do what it says—add and track movies in Radarr—but it needs media-server API secrets and keeps local tracking files.
This looks safe to install if you intentionally want OpenClaw to manage Radarr. Configure the API keys carefully, restrict group/chat access to trusted users, protect the local state directory, and consider fixing the hard-coded workspace paths before depending on the helper scripts.
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.
A trusted user request can cause Radarr to add a movie and start searching for it.
The skill can mutate the Radarr library and start a Radarr movie search. This matches the stated purpose, but it is still an action that can consume storage/network resources.
created = _request("/api/v3/movie", method="POST", body=movie) ... body={"name": "MoviesSearch", "movieIds": [created["id"]]}Restrict who can invoke this skill, especially in group chats, and confirm the movie, quality profile, and root folder when there is ambiguity.
Anyone able to use the configured agent may be able to act through your Radarr/Plex-related credentials within this workflow.
The skill requires a Radarr API key and can optionally use movie-provider and Plex credentials. These are expected for the integration and are not shown being logged or sent to unrelated services.
`RADARR_API_KEY=...` ... `TMDB_API_KEY=...` ... `OMDB_API_KEY=...` ... `PLEX_TOKEN=...`
Store secrets only in the intended OpenClaw environment file, keep them out of chat, and use the narrowest available API permissions or trusted-user allowlists.
Some helper workflows may not work correctly after installation, or may depend on a path outside the installed package.
This helper hard-codes a specific user's workspace path instead of resolving the installed skill path. That is likely a portability/provenance issue rather than malicious behavior, but it could fail or run a different copy if that path exists.
cd /home/vishix/.openclaw/workspace && ./skills/radarr/scripts/radarr.sh
Before relying on this skill, update hard-coded paths to use the current workspace or script-relative paths.
Local state can reveal movie requests and chat identifiers, and tampered state could affect where progress messages are queued.
The tracker persists chat targets and movie notification state in local JSON files so later polling can queue messages. This is disclosed and purpose-aligned, but the state should be treated as private and trusted.
Reads: workspace/state/radarr/tracks/*.json ... Writes: workspace/state/radarr/outbox/*.json ... "channel": channel, "target": str(target)
Keep the OpenClaw workspace state directory private, avoid sharing it, and only let a trusted dispatcher process the Radarr outbox.