Ntfy Cli

v1.0.0

Send push notifications via ntfy.sh or self-hosted ntfy server. Supports priorities, titles, tags, icons, and attachments.

0· 74·0 current·0 all-time
byKrzysztof@genortg

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for genortg/ntfy-cli.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ntfy Cli" (genortg/ntfy-cli) from ClawHub.
Skill page: https://clawhub.ai/genortg/ntfy-cli
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: ntfy
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ntfy-cli

ClawHub CLI

Package manager switcher

npx clawhub@latest install ntfy-cli
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description ask for the ntfy CLI and the SKILL.md only uses the ntfy binary and topic URLs — requiring the ntfy binary is exactly what this skill needs.
Instruction Scope
Instructions are narrowly scoped to invoking the ntfy command with flags and examples. The doc includes an internal example URL (http://genorbox1:9101/email-notification) and warns that topic URLs are secrets; nothing in the instructions tells the agent to read unrelated files or credentials. Note: because topics act as shared secrets, an agent with this skill can send notifications to any reachable topic URL you provide — ensure you trust the agent and the target endpoints.
Install Mechanism
No install spec is present (instruction-only). The skill expects the ntfy binary to already be installed; this is low-risk and consistent with the skill's purpose.
Credentials
The skill requests no environment variables, credentials, or config paths. That aligns with using a local ntfy binary and passing topic URLs at runtime.
Persistence & Privilege
always is false and the skill does not request persistent privileges or modify other skills; autonomous invocation is allowed by default but that is normal for skills of this type.
Assessment
This skill is coherent and only runs the ntfy CLI. Before installing, ensure you: (1) have the official ntfy binary from a trusted source, (2) do not expose sensitive ntfy topic URLs in public logs or prompts (topics are effectively secrets), and (3) are comfortable letting the agent send notifications to any topic URL you supply (including internal hosts). If you want tighter control, restrict which topics the agent may use or avoid granting it access to topics that act as tokens for other services.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🔔 Clawdis
Binsntfy
latestvk97a7p0ebwwfzgdrnvkbv378n985d5c0
74downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

ntfy CLI Skill

Send push notifications using the ntfy command-line tool. Agents can use this to alert Genor on his devices.

Installation

Ensure ntfy is installed on the system:

# On Debian/Ubuntu
sudo apt install ntfy

# Or download binary from https://ntfy.sh/

Verify with ntfy --version.

Basic Usage

The simplest form: push a message to a topic (which is just a URL endpoint).

ntfy send <topic_url> "<message>"

Example (as tested by Genor):

ntfy send http://genorbox1:9101/email-notification "HEJ"

Advanced Options

Title

ntfy send --title "Alert from Email Emily" <topic_url> "message"

Priority

Priorities: max, high, default, low, min

ntfy send --priority high <topic_url> "Important message"

Tags (emojis)

ntfy send --tags warning,skull <topic_url> "Something went wrong"

Markdown formatting

ntfy send --markdown <topic_url> "**Bold** and *italic* text"

Click action (open URL when tapped)

ntfy send --click "https://example.com" <topic_url> "Open dashboard"

Attachments (from URL)

ntfy send --attach "https://example.com/image.png" <topic_url> "See attached"

Combining options

ntfy send \
  --title "Server down" \
  --priority max \
  --tags warning,skull \
  --click "https://statuspage.example.com" \
  <topic_url> "Server xy01 is unreachable"

Topic URL Format

  • Self-hosted: http://your-server:port/topic-name or https://your-server/topic-name
  • ntfy.sh cloud: https://ntfy.sh/topic-name

Topics are essentially passwords; choose something not easily guessable.

When to Use

  • Urgent alerts that need immediate attention (use --priority max or high)
  • Informational notifications (use low or min)
  • Email notifications (Email Emily)
  • System health warnings
  • Monitoring alerts

Best Practices

  • Always include a clear, concise message
  • Use priority appropriately to avoid alert fatigue
  • Tag messages with relevant emojis for quick visual scanning
  • For critical alerts, consider adding a click action to open a dashboard or runbook
  • Keep topic names secret if you want to restrict who can send notifications

Agent Integration

When an agent needs to notify Genor via ntfy:

  1. Build the message content
  2. Use ntfy send with appropriate flags
  3. Choose priority based on urgency
  4. Add tags for context (e.g., email-emily, health-check)

Example from Email Emily:

ntfy send \
  --title "New important email" \
  --priority high \
  --tags email,important \
  http://genorbox1:9101/email-notification "From: john@example.com\nSubject: Project update..."

Security Note

The ntfy topic URL is effectively a shared secret. Do not expose it in logs or public channels. Only use it within secure environments.


ntfy-cli skill for OpenClaw agents - Updated 2026-04-02

Comments

Loading comments...