Sabnzbd

Manage Usenet downloads with SABnzbd. Use when the user asks to "check SABnzbd", "list NZB queue", "add NZB", "pause downloads", "resume downloads", "SABnzbd status", "Usenet queue", "NZB history", or mentions SABnzbd/sab download management.

This skill appears to do what it says — a CLI wrapper around the SABnzbd API — but there are a few things to check before installing: - The metadata omits required runtime items: the helper script expects an API key and URL (stored in ~/.clawdbot/credentials/sabnzbd/config.json or via SAB_API_KEY/SAB_URL/SAB_CONFIG) and relies on curl, jq, and python3. Make sure those binaries are present and that the skill owner adds these to the declared requirements. - The API key is sensitive. The skill will send that key to whichever SAB URL you configure. Only point it at a trusted SABnzbd instance (typically localhost or a machine you control). Do not point it at unknown remote hosts. - Inspect scripts/sab-api.sh yourself (you already have it); it appears to call only the configured SABnzbd URL and has no hidden external endpoints, but you should verify there are no modifications beyond what's included here. - Consider filesystem permissions for ~/.clawdbot/credentials/sabnzbd/config.json so other users/processes cannot read your API key. If you accept these conditions and trust the source, the skill is usable; if you require strict metadata-to-behavior alignment, ask the publisher to declare the env vars and required binaries before enabling it.

Type: OpenClaw Skill Name: sabnzbd Version: 1.0.0 The skill is designed to manage SABnzbd downloads via its REST API. It reads API credentials from a standard OpenClaw configuration path (`~/.clawdbot/credentials/sabnzbd/config.json`) or environment variables and uses `curl` to interact with the specified SABnzbd instance. The `SKILL.md` and `README.md` files provide clear, benign instructions for the agent and user, without any evidence of prompt injection attempts or instructions to perform unauthorized actions. The `sab-api.sh` script's functionality is entirely aligned with SABnzbd management, including adding local NZB files, which is a legitimate function, not an attempt at arbitrary file exfiltration. No malicious execution, persistence mechanisms, or unauthorized data exfiltration attempts were found.