skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
gitstua/stu-skills81 installs

ntfy-notify

Send push notifications via ntfy.sh with a lightweight shell workflow. Use when posting alerts, job status updates, reminders, or automation results to an ntfy topic using token auth or public topics.

How do I install this agent skill?

npx skills add https://github.com/gitstua/stu-skills --skill ntfy-notify
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is safe and provides a utility for sending push notifications via the ntfy.sh service. It uses a local shell script to communicate with the ntfy API and follows standard security practices by storing configuration and access tokens in a local environment file.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    2/3 files flagged

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

ntfy Notify

Use scripts/ntfy_send.sh for deterministic, low-overhead notifications.

Prerequisites

  • Required default topic: NTFY_DEFAULT_TOPIC
    • Example: export NTFY_DEFAULT_TOPIC="my-topic"
  • Optional auth: NTFY_ACCESS_TOKEN (script also accepts legacy NTFY_TOKEN)
    • Example: export NTFY_ACCESS_TOKEN="<your-ntfy-access-token>"
  • Secrets/defaults file: ~/.config/stu-skills/ntfy-notify/.env
    • The script reads this path from ntfy-notify/.env-path automatically.
  • If NTFY_DEFAULT_TOPIC is missing and --topic is not passed, the script exits with an instruction for the agent to ask the user for it.

Configure

  1. Set a default topic:
    • export NTFY_DEFAULT_TOPIC="my-topic"
  2. Optionally set token auth:
    • export NTFY_ACCESS_TOKEN="<your-ntfy-access-token>"
  3. Optional custom server (default is https://ntfy.sh):
    • export NTFY_SERVER="https://ntfy.sh"
  4. Recommended: store values in ~/.config/stu-skills/ntfy-notify/.env so the agent only executes the script and does not need secret values inline.
    • Example:
      • NTFY_DEFAULT_TOPIC="my-topic"
      • NTFY_ACCESS_TOKEN="<your-ntfy-access-token>"
      • NTFY_SERVER="https://ntfy.sh"

.env Sample

Path: ~/.config/stu-skills/ntfy-notify/.env

NTFY_DEFAULT_TOPIC="my-topic"
NTFY_ACCESS_TOKEN="<your-ntfy-access-token>"
NTFY_SERVER="https://ntfy.sh"

Send

  • Basic:
    • scripts/ntfy_send.sh "Build finished"
  • Explicit topic:
    • scripts/ntfy_send.sh --topic ops-alerts "Backup completed"
  • Add title/priority/tags:
    • scripts/ntfy_send.sh --title "Deploy" --priority 4 --tags rocket,white_check_mark "Release shipped"

Notes

  • Prefer env vars for secrets and defaults.
  • --dry-run redacts bearer token values in printed curl output.
  • Keep messages short and actionable.
  • Use --dry-run to verify payload/header behavior without network calls.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/gitstua/stu-skills/ntfy-notify">View ntfy-notify on skillZs</a>