stacks-push

Send push notifications via Expo and Firebase Cloud Messaging services.

2|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/bughq/bughq --skill stacks-push-bughq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-push
Source: https://github.com/bughq/bughq/tree/main/.claude/skills/stacks-push
Command: npx skills add https://github.com/bughq/bughq --skill stacks-push-bughq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stacksjs/types, @stacksjs/cli.

What problem does it solve?

This Skill simplifies the complex process of managing push notifications across different providers, abstracting the differences between Expo and Firebase Cloud Messaging (FCM) into a unified interface.

Core Features & Use Cases

  • Unified Driver Interface: Send notifications via Expo or FCM using a single, consistent function call.
  • Advanced FCM Support: Handles both legacy server keys and modern v1 service account APIs, including JWT generation and OAuth2 token exchange.
  • Use Case: If your application needs to alert users on both iOS and Android, use this Skill to batch send notifications to specific device tokens or broadcast messages to topic subscribers without writing separate logic for each provider.

Quick Start

Use the stacks-push skill to send a high-priority notification with a custom data payload to a specific device token using the Expo driver.

Frequently Asked Questions about stacks-push

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

FAQPage Schema
How do I send cross-platform push notifications via Expo and Firebase Cloud Messaging using a single interface?

You can send cross-platform push notifications via Expo and FCM using a unified driver interface that abstracts token validation and payload mapping into a single consistent function call, eliminating the need to write separate provider logic.

Does this FCM integration support modern v1 service account APIs and OAuth2 token exchange?

Yes, the FCM integration supports modern v1 service account APIs by handling JWT generation and OAuth2 token exchange natively, while also maintaining backward compatibility with legacy server keys for secure credential handling.

What is the best way to batch send push notifications to multiple device tokens?

The best way to batch send push notifications is using the built-in batch processing feature, which allows you to deliver custom data payloads to specific device tokens or broadcast messages to topic subscribers across iOS and Android.

Can I use topic subscriptions for broadcasting mobile push notifications across different providers?

Yes, you can use topic subscriptions to broadcast mobile push notifications, abstracting the delivery logic across both Expo and Firebase Cloud Messaging to reach targeted audience segments consistently.

Why do I need to validate device tokens when integrating Firebase Cloud Messaging?

You need to validate device tokens when integrating FCM to ensure payload mapping accuracy and verify delivery receipts, preventing failed notification dispatches to invalid or expired mobile device endpoints.