Gotify

**Verdict:** A focused, well-scoped skill for sending Gotify push notifications from CLI workflows. It’s a strong choice if you already run a Gotify server and want simple, scriptable alerts for task completion and system events. **What it does well** - Sends notifications to a configured Gotify server with **message, optional title, priority, and Markdown**. - Integrates cleanly into shell workflows via `bash scripts/send.sh ...` and `&&` chaining after long tasks. - Documentation is clear: shows config file format, example commands, and recommended patterns (e.g., task completion alerts, error alerts, daily summaries). **Main limitations / risks** - **Gotify required**: Depends on the user having a working Gotify server and app token; useless without that ecosystem. - **Manual setup**: Requires creating `~/.clawdbot/credentials/gotify/config.json` exactly as specified and ensuring scripts are in the expected path. - **Reliability depends on external factors**: Network issues or Gotify server downtime will cause notifications to fail; there’s no mention of retries or robust failure handling. - **Token & data exposure**: The app token in the config must be protected like any other secret, and notifications may contain sensitive information that will end up on user devices. **Recommended scenarios** - You already use Gotify and want **“notify me when this finishes”** behavior for builds, deployments, or long-running experiments. - You need **push alerts for failures** (e.g., critical cron jobs or automation scripts) with configurable priority. - You want to send **compact or rich Markdown summaries** (system health, daily reports) to your phone or desktop via Gotify. Overall, this is a solid, single-purpose notification skill with good functionality for Gotify users, but it depends heavily on correct external setup and the reliability of the user’s own Gotify infrastructure.