Radarr

**Judgement:** A solid, focused skill for managing a self-hosted Radarr library via scripts. Well-suited for users who already run Radarr and want their assistant to handle movie search, addition (including collections), and removal. **Key strengths:** - Covers the main Radarr workflows (search, exists, add, add-collection, remove, config) with clear CLI commands. - Enforces good presentation of search results by requiring TMDB links, which improves user clarity and reduces mis-selection. - Collection-aware: can prompt to add entire collections when relevant, reducing repetitive work. - Clear configuration model via `config.json` specifying Radarr URL, API key, and default quality profile. **Risks & limitations:** - Safety risk around deletion: although the interface specifies to always ask the user before deleting files, the underlying `--delete-files` flag can remove media permanently if misused or if the assistant fails to confirm correctly. - Depends on a correctly configured local Radarr instance (`http://localhost:7878` or custom URL) and valid API key; misconfiguration will cause failures. - Functionality is intentionally narrow to Radarr; it does not manage related services (e.g., download clients) and assumes Radarr handles those. **Recommended scenarios:** - Home media server users who already run Radarr and want conversational control over adding movies and collections. - Assistants that help users build or maintain curated movie libraries with quality profiles and clear disambiguation via TMDB links. - Environments where file deletion is acceptable but must be tightly controlled by explicit user confirmation before invoking `--delete-files`.