implement-push-notifications

Implement mobile push notification delivery using APNs and FCM HTTP v1 protocols.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill implement-push-notifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-push-notifications
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/implement-push-notifications
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill implement-push-notifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of implementing reliable mobile push notifications, handling the fragmented requirements of APNs and FCM across different app states and device platforms.

Core Features & Use Cases

  • Unified Provider Setup: Configures APNs token-based auth and FCM HTTP v1 for cross-platform delivery.
  • Lifecycle Management: Handles token registration, rotation, and dead-token cleanup to ensure high delivery rates.
  • Payload Design: Provides schemas for alert, silent, and rich media notifications with deep-linking support.
  • Use Case: Use this skill to implement a robust notification system that ensures users receive timely alerts, handles background data synchronization, and correctly routes users to specific app screens upon tapping a notification.

Quick Start

Use the implement-push-notifications skill to configure the FCM HTTP v1 provider and set up the device token registration logic for my mobile application.

Frequently Asked Questions about implement-push-notifications

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

FAQPage Schema
How do I implement push notifications for both iOS and Android using FCM and APNs?

Push notifications are handled by configuring APNs token-based auth and FCM HTTP v1 protocols for cross-platform delivery. This setup manages device token registration, payload schema design, and receipt handling across both iOS and Android platforms.

How do push notifications work when my mobile app is in the background or killed state?

Push notifications in background or killed states are managed through silent and alert payload schemas. The system handles receipt processing across foreground, background, and killed app states to ensure proper data synchronization and user alert delivery.

What is the best way to handle FCM device token rotation and dead token cleanup?

The best way to handle device token rotation is through lifecycle management that tracks token registration and performs dead-token cleanup. This ensures high delivery rates by removing invalid tokens and managing rotation properly.

How do I add deep linking to mobile push notification payloads?

Deep linking in push notification payloads is configured through payload schema design that supports rich media notifications. This allows the system to correctly route users to specific app screens upon tapping a notification.

Why are my silent push notifications not being delivered on iOS?

Silent push notifications on iOS may fail due to incorrect payload schema design or improper handling of background app states. Verifying APNs token-based auth setup and background state receipt handling ensures robust delivery for data synchronization.