Qbittorrent

**Judgement:** A capable and focused skill for managing a local qBittorrent instance via its WebUI API. It is well-suited for automation and remote control of torrent workflows, assuming the host environment is correctly configured. **What it does well:** - Provides end-to-end torrent lifecycle control: list, filter, add (magnet/URL/file), pause/resume, delete (optionally removing files), and recheck. - Exposes useful metadata (state, speeds, ETA, size, progress, categories/tags, save path) plus finer-grained info (files, trackers). - Supports global transfer and app-level queries (speed limits, transfer stats, preferences, version), which is valuable for system-wide management. **Risks / Concerns:** - **Legal/Content risk:** Torrent management can be used for copyright infringement. The tool itself is neutral, but any deployment should enforce policies that prohibit illegal content and respect local laws. - **Security & privacy:** Requires storing qBittorrent credentials locally. Misconfiguration (default `admin/adminadmin`, weak passwords, or exposing the WebUI to untrusted networks) can lead to unauthorized control of the client and visibility into downloaded content. - **Environment coupling:** Assumes qBittorrent WebUI is reachable at the configured URL and version (v4.1+). If the service is down, moved, or reconfigured, calls will fail. **Recommended scenarios:** - Users who explicitly request to manage a **local** qBittorrent instance: listing active downloads, checking progress, or querying speeds. - Automation around scheduled or rule-based torrent management: categorizing new torrents, applying tags, or adjusting speed limits at certain times. - Tech-savvy users running home servers/NAS who want voice/assistant integration for their qBittorrent client. **When to be cautious or avoid:** - When user intent clearly involves pirated or otherwise illegal content; the assistant should refuse such requests even though the skill is capable. - In multi-tenant or shared environments without clear access controls, where exposing torrent info or control might violate privacy or policy. - If the deployment cannot ensure secure credential storage and restricted network access to the qBittorrent WebUI.