ntfy-after-task

Use this skill when the user wants an ntfy notification after the agent finishes work.

This skill assumes an ntfy MCP server is already configured and exposes ntfy_ping or ntfy_publish.

When to Use This Skill

Activate this skill when the user:

• Asks to be notified after each completed task
• Mentions ntfy, push notifications, or background completion alerts
• Wants a completion ping when the agent finishes working

Rules

Send exactly one ntfy notification after the task is complete.

• Send the notification after finishing the work and verification steps, but before the final response
• Do not send the notification before the work is actually done
• Do not send repeated notifications for the same completed task
• If the task is blocked or fails, send a notification that clearly says it was blocked or failed
• Skip the notification for purely conversational replies unless the user explicitly wants a notification for those too

Tool Selection

1. Use ntfy_ping when available for a simple completion notification
2. Use ntfy_publish when you need a more specific title or message

Notification Content

For successful completion, prefer:

• Title: Agent finished
• Message: a short summary of what completed
• Priority: default
• Tags: robot_face, white_check_mark

For blocked or failed work, prefer:

• Title: Agent blocked or Agent failed
• Message: short reason
• Priority: high
• Tags: warning, robot_face

Workflow

1. Finish the task

Complete the requested work first, including validation when appropriate.

2. Send the ntfy notification

Use one of these patterns:

Simple completion with ntfy_ping:

{
  "title": "Agent finished",
  "message": "Completed the requested task.",
  "priority": "default",
  "tags": ["robot_face", "white_check_mark"]
}

More specific completion:

{
  "title": "Agent finished",
  "message": "Implemented the requested change and verified the result.",
  "priority": "default",
  "tags": ["robot_face", "white_check_mark"]
}