Radarr+

**Judgement:** A solid, well-scoped skill for integrating Radarr into chat and automation workflows, particularly suited to self-hosted media setups where users request/download movies via Radarr/Plex. **What it does well:** - Covers the main Radarr operations needed for chat-based movie requests: lookup (by term or TMDB id), listing quality profiles and root folders, adding movies with monitoring and search, and tracking progress to completion. - Offers a clear recommended chat workflow (lookup → config resolution → optional rich card → add → progress tracking), making it straightforward to integrate into bots and cron runners. - Optional TMDB/OMDB/Plex integrations allow rich movie cards and Plex playback links, improving end-user experience without being strictly required. **Key risks / limitations:** - Requires a correctly configured Radarr instance and environment variables (URL, API key, optional TMDB/OMDB/Plex). Misconfiguration will cause failures that need operational troubleshooting. - File-based tracking and polling introduce some operational complexity (cron/runner management, filesystem permissions) and potential fragility under heavy usage. - No built-in rate limiting or access control; if exposed to untrusted users, it could be abused to enqueue many downloads on the Radarr host. **Recommended scenarios:** - Self-hosted Radarr/Plex environments where a small group of trusted users want to request movies from within chat (Telegram or similar) and see progress updates until import. - OpenClaw deployments aiming to provide a “movie request bot” front-end instead of giving users direct access to the Radarr web UI. - Media automation setups where Radarr workflows (add + monitor + search) need to be triggered programmatically with human-friendly feedback and configuration resolution.