sk-notifications

Dispatch user notifications across in-app, email, and push channels.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-notifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sk-notifications
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/sk-notifications
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-notifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the complexity of delivering in-app, email, and push notifications reliably while respecting each user’s category preferences and per-device push state.

Core Features & Use Cases

  • Server-side notification dispatch (notify): Resolve effective channels from category defaults plus user preferences, insert records, and fan out to in-app, email, and push.
  • Visibility-aware polling endpoint (/api/notifications/poll): Fetch the latest notifications and unread count in a Vercel-friendly way using serverless polling with dynamic behavior.
  • Client integration (useNotifications) and UI components: Provide a ready-to-use bell/panel/settings experience, including per-device push subscription management via PushDevicesList.
  • Central SSOT configuration (src/config/notifications.ts): Manage the categories × channels model in one place so the rest of the system stays consistent.

Quick Start

Use the sk-notifications Skill to dispatch a notification from a server action with notify() and wire the bell and settings UI so users can see, read, delete, and manage delivery preferences including push per device.

Frequently Asked Questions about sk-notifications

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

FAQPage Schema
How do I send notifications across in-app, email, and push while respecting per-user preferences?

To send notifications across in-app, email, and push while respecting per-user preferences, use a server-side dispatch function that resolves effective channels from category defaults and user settings before fanning out the delivery.

How does visibility-aware polling work for notifications on Vercel serverless?

Visibility-aware polling on Vercel serverless uses a dedicated API endpoint to fetch the latest notifications and unread counts dynamically. This approach ensures efficient polling behavior without keeping connections open.

What is the best way to manage multi-device push subscriptions in a Next.js app?

The best way to manage multi-device push subscriptions in a Next.js app is to implement a UI component that lists registered devices and allows users to control their push delivery preferences per device.

Do I need a central configuration to manage notification categories and channels?

You need a central configuration source of truth to manage notification categories and channels. This keeps the category defaults and channel model consistent across server dispatch and client UI components.

Can I use server actions to dispatch durable notifications?

You can use server actions to dispatch durable notifications by inserting records into storage and fanning out to in-app, email, and push channels directly from the server action execution.

What are the limitations of polling notifications versus using a persistent connection?

Polling notifications relies on repeated client requests to an endpoint rather than a persistent connection, meaning updates are only as fresh as the polling interval and may incur higher serverless function invocations.