Universal Notify

Send notifications through multiple channels with a single script. Supports ntfy.sh (free, no signup), Gotify (self-hosted), generic webhooks, email (SMTP/curl), Telegram Bot API, and Pushover. Use when sending alerts, monitoring notifications, deployment notices, or any event that needs to reach a human through their preferred channel. Unified interface with priority levels (low/normal/high/urgent).

Security Scan

This is a small, coherent notification script that does what it claims (send messages to ntfy, Gotify, webhooks, email, Telegram, and Pushover); there are no hidden endpoints or surprising requirements, but exercise caution when supplying credentials on the command line because they can be exposed.

Purpose & Capability

The name/description match the provided implementation: scripts/notify.sh implements ntfy, Gotify, webhook, email, Telegram, and Pushover channels. It requires only curl (documented) and uses CLI arguments for channel credentials, which is consistent with the stated purpose.

Instruction Scope

SKILL.md simply documents usage of scripts/notify.sh and examples match the script. The script performs only network calls to user-supplied URLs and known service endpoints (ntfy.sh, api.telegram.org, api.pushover.net). It does not read other files or environment variables. Note: passing secrets (tokens, SMTP URLs) as CLI args exposes them to process listings and shell history — the docs/examples encourage this pattern, which raises privacy risks even though it's functionally coherent.

Install Mechanism

No install spec — instruction-only plus a single shell script. Nothing is downloaded or installed automatically, so there is minimal install-time risk.

Credentials

The skill declares no required environment variables or credentials and expects credentials as CLI arguments, which is proportionate to its function. However, supplying tokens/keys on the command line can leak them via ps/shell history; consider safer approaches (environment variables, config files with proper permissions) before use.

Persistence & Privilege

always is false and the skill does not request persistent/system-wide configuration or modify other skills. It runs only when invoked and does not enable autonomous background behavior.

Assessment

The script is small and implements exactly the channels described. Before installing or using it: 1) verify the endpoints you provide (especially custom Gotify/webhook URLs) are trusted; 2) avoid passing secrets on the command line (they are visible to other users via process listings and recorded in shell history) — prefer setting them in a protected env or a restricted config file and modifying the script to read them; 3) ensure TLS is used for URLs that carry sensitive payloads; and 4) because the skill source/homepage is unknown, inspect the script locally and consider pinning a vetted copy in your environment rather than pulling from an untrusted registry.

Send notifications via scripts/notify.sh:

# ntfy.sh (free, no auth needed)
scripts/notify.sh --channel ntfy --topic myalerts --message "Disk 90%!" --priority urgent

# Gotify (self-hosted)
scripts/notify.sh --channel gotify --url https://gotify.local --token TOKEN --message "Deploy done"

# Webhook (generic JSON POST)
scripts/notify.sh --channel webhook --url https://hooks.example.com/abc --message "Event fired"

# Email
scripts/notify.sh --channel email --smtp smtp://mail:587 --from [e-mail] --to [e-mail] --subject "Alert" --message "Check server"

# Telegram
scripts/notify.sh --channel telegram --bot-token BOT:TOK --chat-id 12345 --message "Hello"

# Pushover
scripts/notify.sh --channel pushover --app-token X --user-key Y --message "Alert" --priority high

Common Options

All channels support --message (required), --title (optional), and --priority low|normal|high|urgent (default: normal).

Requirements

• curl (standard on most systems)
• No API keys needed for ntfy.sh — other channels require their respective credentials