Gotify

Send push notifications via Gotify when long-running tasks complete or important events occur. Use when the user asks to "send a Gotify notification", "notify me when this finishes", "push notification", "alert me via Gotify", or wants to be notified of task completion.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 2.3k · 6 current installs · 6 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, required binaries (curl, jq), and included script align with a Gotify notification skill. Minor inconsistency: registry metadata lists no required config paths/env vars, but SKILL.md and scripts expect a credentials file at ~/.clawdbot/credentials/gotify/config.json (and the script supports overriding that path via GOTIFY_CONFIG_FILE).
Instruction Scope
SKILL.md instructs the agent to call the included send.sh script and to create a local credentials JSON. The instructions stay within the stated purpose (sending notifications) and do not request unrelated files or secrets beyond the Gotify token/config file. Examples reference integrating the script into command workflows.
Install Mechanism
No install spec (instruction-only plus a small shell script). Nothing is downloaded or installed automatically, so runtime risk is low and actions are visible on disk.
Credentials
The skill does not require broad credentials; it only needs a Gotify URL and application token. Minor documentation mismatch: README mentions alternative environment variables GOTIFY_URL/GOTIFY_TOKEN, but the actual script reads a config JSON (or an override path via GOTIFY_CONFIG_FILE). No unexpected credentials are requested.
Persistence & Privilege
Skill does not request always: true and does not attempt to modify other skills or system settings. It runs on explicit invocation (or when the agent decides to invoke it) and only sends notifications to the configured Gotify endpoint.
Assessment
This skill appears to do exactly what it says: a small bash script posts messages to your Gotify server. Before installing, verify the following: (1) create the credentials file at ~/.clawdbot/credentials/gotify/config.json (or set GOTIFY_CONFIG_FILE to point to it) since the script does not actually read GOTIFY_URL/GOTIFY_TOKEN despite README text claiming that option; (2) keep the config file readable only by the intended user (tokens are sensitive); (3) the script sends the token in the URL query string (message?token=...), which may be logged by intermediaries—prefer HTTPS and confirm your Gotify endpoint is trusted; (4) review and test the script locally to confirm behavior and response handling (it prints the raw response); and (5) because the skill will contact whatever GOTIFY_URL you configure, ensure that host is correct and trusted. These are operational/privacy cautions rather than indications of malicious intent.

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

Current versionv1.0.1
Download zip
latestvk97288vhw7pevw528ma2jxhngd7zsssa

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🔔 Clawdis
Binscurl, jq

SKILL.md

Gotify Notification Skill

Send push notifications to your Gotify server when long-running tasks complete or important events occur.

Purpose

This skill enables Clawdbot to send push notifications via Gotify, useful for:

  • Alerting when long-running tasks complete
  • Sending status updates for background operations
  • Notifying of important events or errors
  • Integration with task completion hooks

Setup

Create the credentials file: ~/.clawdbot/credentials/gotify/config.json

{
  "url": "https://gotify.example.com",
  "token": "YOUR_APP_TOKEN"
}
  • url: Your Gotify server URL (no trailing slash)
  • token: Application token from Gotify (Settings → Apps → Create Application)

Usage

Basic Notification

bash scripts/send.sh "Task completed successfully"

With Title

bash scripts/send.sh --title "Build Complete" --message "skill-sync tests passed"

With Priority (0-10)

bash scripts/send.sh -t "Critical Alert" -m "Service down" -p 10

Markdown Support

bash scripts/send.sh --title "Deploy Summary" --markdown --message "
## Deployment Complete

- **Status**: ✅ Success
- **Duration**: 2m 34s
- **Commits**: 5 new
"

Integration with Task Completion

Option 1: Direct Call After Task

# Run long task
./deploy.sh && bash ~/clawd/skills/gotify/scripts/send.sh "Deploy finished"

Option 2: Hook Integration (Future)

When Clawdbot supports task completion hooks, this skill can be triggered automatically:

# Example hook configuration (conceptual)
{
  "on": "task_complete",
  "run": "bash ~/clawd/skills/gotify/scripts/send.sh 'Task: {{task_name}} completed in {{duration}}'"
}

Parameters

  • -m, --message <text>: Notification message (required)
  • -t, --title <text>: Notification title (optional)
  • -p, --priority <0-10>: Priority level (default: 5)
    • 0-3: Low priority
    • 4-7: Normal priority
    • 8-10: High priority (may trigger sound/vibration)
  • --markdown: Enable markdown formatting in message

Examples

Notify when subagent finishes

# After spawning subagent
sessions_spawn --task "Research topic" --label my-research
# ... wait for completion ...
bash scripts/send.sh -t "Research Complete" -m "Check session: my-research"

Notify on error with high priority

if ! ./critical-task.sh; then
  bash scripts/send.sh -t "⚠️ Critical Failure" -m "Task failed, check logs" -p 10
fi

Rich markdown notification

bash scripts/send.sh --markdown -t "Daily Summary" -m "
# System Status

## ✅ Healthy
- UniFi: 34 clients
- Sonarr: 1,175 shows
- Radarr: 2,551 movies

## 📊 Stats
- Uptime: 621h
- Network: All OK
"

Workflow

When the user says:

  • "Notify me when this finishes" → Add && bash scripts/send.sh "Task complete" to their command
  • "Send a Gotify alert" → Run bash scripts/send.sh with their message
  • "Push notification for task completion" → Integrate into their workflow with appropriate title/priority

Always confirm the notification was sent successfully (check for JSON response with message ID).

Notes

  • Requires network access to your Gotify server
  • App token must have "create message" permission
  • Priority levels affect notification behavior on client devices
  • Markdown support depends on Gotify client version (most modern clients support it)

Reference

Files

3 total
Select a file
Select a file to preview.

Comments

Loading comments…