skills.rest
yuki-yano
yuki-yanoCOMMUNITY
Explore all skills by this author →
𝕏@yuki_ycinoGitHub

ntfy-mobile-notify

Send mobile notifications via ntfy when explicitly requested with validated formatting.

64|2|Updated Feb 8, 2018
Search Tags:#automation#mobile#alerts#shell#notify#ntfy
One-click install
npx skills add https://github.com/yuki-yano/dotfiles --skill ntfy-mobile-notify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ntfy-mobile-notify
Source: https://github.com/yuki-yano/dotfiles/tree/main/.agents/skills/ntfy-mobile-notify
Command: npx skills add https://github.com/yuki-yano/dotfiles --skill ntfy-mobile-notify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

## What problem does it solve? This skill standardizes sending smartphone notifications via ntfy, ensuring they are only sent when explicitly requested, and validates the presence of NTFY_TOPIC, enforces a consistent title format, and enforces a 100-200 character summary.

## Core Features & Use Cases

  • Policy-based notifications: only send mobile alerts when the user explicitly asks for them.
  • Environment and formatting checks: requires NTFY_TOPIC and enforces the title pattern [REPO_NAME] {Codex|Claude Code} ..., plus a 100-200 character summary.
  • Quick Start guidance: see the Quick Start example to trigger a mobile notification using --summary and optional parameters.

### Quick Start Provide a 100-200 character summary with --summary, optionally set --title-suffix and --agent, and run the script to publish the notification.

Frequently Asked Questions about ntfy-mobile-notify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send mobile alerts from a shell script without getting unwanted notifications?▼

Mobile alerts are sent from shell scripts only when explicitly requested, reducing notification noise by enforcing that NTFY_TOPIC is set and validating a 100-200 character summary before publishing.

What's the best way to get notified on my phone when a build or deployment finishes?▼

Getting notified on your phone after builds or deployments uses ntfy to deliver controlled mobile alerts, requiring a 100-200 character summary and a formatted title to ensure clear, relevant event updates.

Do I need to set environment variables to use ntfy for automation alerts?▼

Using ntfy for automation alerts requires the NTFY_TOPIC environment variable to be set, enforcing consistent routing and title formatting for mobile notifications across project tasks.

Can I test sending a mobile notification without actually delivering it to my phone?▼

Testing a mobile notification without delivery is supported through a dry-run mode, allowing you to validate the summary length, title format, and parameters before publishing the alert.

How do I format the title for automated mobile alerts across different agents?▼

Formatting the title for automated mobile alerts requires the pattern [REPO_NAME] {Codex|Claude Code} ..., and supports optional title-suffix and agent overrides to customize the notification source.

Why are my ntfy mobile notifications failing to send from my automation flow?▼

ntfy mobile notifications fail to send when the NTFY_TOPIC environment variable is missing, the summary is not 100-200 characters, or the title format does not match the required pattern.

Related Skills

Explore More Software Engineering Skills→
istota-projectistota-project
10

ntfy

Send one-way push notifications to configured ntfy topics with optional headers.

Official
Intermediate
JansenAnalyticsJansenAnalytics
5

ntfy

Send real-time push notifications to devices via ntfy topics.

Community
Basic
Leeky1017Leeky1017
1

Synopsis

Generate a 200-300 character single-paragraph synopsis from chapter content.

Community
Intermediate
multicammulticam

notify

Send real-time push alerts to users via ntfy.sh with a required message.

Community
Basic