How do I install the Usernotifications skill?

Run npx skillmds@latest add caglarbaranbora/usernotifications in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Usernotifications safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Usernotifications?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Usernotifications free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Usernotifications?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Usernotifications by caglarbaranbora

Name: Usernotifications
Author: caglarbaranbora

Usernotifications

Route UserNotifications framework implementation tasks to the correct Knowledge Contracts -- authorization, local notification scheduling, remote push registration, delegate handling, actions/categories, and managing pending/delivered requests plus badge count. Use when calling UNUserNotificationCenter, requestAuthorization, UNAuthorizationOptions, getNotificationSettings, UNMutableNotificationContent, UNNotificationRequest, UNTimeIntervalNotificationTrigger, UNCalendarNotificationTrigger, registerForRemoteNotifications, didRegisterForRemoteNotificationsWithDeviceToken, UNUserNotificationCenterDelegate, willPresent, didReceive, UNNotificationAction, UNTextInputNotificationAction, UNNotificationCategory, setNotificationCategories, removePendingNotificationRequests, removeDeliveredNotifications, or badge count / setBadgeCount. v1 is client-side UserNotifications + UIKit push-registration API only -- no rich media extensions, critical alerts, location triggers, APNs server payloads, Live Activities, or watchOS.

File contents

UserNotifications — Foundations Skill

Purpose

Route UserNotifications framework implementation tasks to the minimum required UserNotifications Knowledge Contracts. v1 scope is client-side API implementation only: authorization, local scheduling, push registration, delegate handling, actions/categories, and pending/delivered/badge management.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/usernotifications/.

Calling requestAuthorization, UNAuthorizationOptions, or getNotificationSettings -> authorization-request.md
Building UNMutableNotificationContent/UNNotificationRequest or configuring a trigger -> local-notification-scheduling.md
Calling registerForRemoteNotifications or handling its device-token callbacks -> remote-push-registration.md
Setting UNUserNotificationCenterDelegate, willPresent, or didReceive -> notification-delegate-handling.md
Defining UNNotificationAction/UNTextInputNotificationAction/UNNotificationCategory or setNotificationCategories -> notification-actions-and-categories.md
Removing/inspecting pending or delivered requests, or setting badge count -> managing-pending-delivered-and-badge.md

Never load more than the contracts relevant to the specific question.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/usernotifications/ — do not guess or fall back to general knowledge. UNNotificationServiceExtension/UNNotificationContentExtension rich-media extensions, critical-alert entitlement specifics, location-based triggers (UNLocationNotificationTrigger), APNs server-side payload construction, ActivityKit/Live Activities, and watchOS-specific notification interfaces are deferred/unbuilt scope — report that explicitly rather than answering from general knowledge (see docs/architecture/domain-map.md). Notification design questions (content wording, timing judgment, foreground UX, badge conventions) are owned by the human-interface-guidelines Skill, not this one.

---name: usernotificationsdescription: Route UserNotifications framework implementation tasks to the correct Knowledge Contracts -- authorization, local notification scheduling, remote push registration, delegate handling, actions/categories, and managing pending/delivered requests plus badge count. Use when calling UNUserNotificationCenter, requestAuthorization, UNAuthorizationOptions, getNotificationSettings, UNMutableNotificationContent, UNNotificationRequest, UNTimeIntervalNotificationTrigger, UNCalendarNotificationTrigger, registerForRemoteNotifications, didRegisterForRemoteNotificationsWithDeviceToken, UNUserNotificationCenterDelegate, willPresent, didReceive, UNNotificationAction, UNTextInputNotificationAction, UNNotificationCategory, setNotificationCategories, removePendingNotificationRequests, removeDeliveredNotifications, or badge count / setBadgeCount. v1 is client-side UserNotifications + UIKit push-registration API only -- no rich media extensions, critical alerts, location triggers, APNs server payloads, Live Activities, or watchOS.---# UserNotifications — Foundations Skill## PurposeRoute UserNotifications framework implementation tasks to the minimumrequired UserNotifications Knowledge Contracts. v1 scope is client-sideAPI implementation only: authorization, local scheduling, pushregistration, delegate handling, actions/categories, andpending/delivered/badge management.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/usernotifications/.- Calling requestAuthorization, UNAuthorizationOptions, or getNotificationSettings -> authorization-request.md- Building UNMutableNotificationContent/UNNotificationRequest or configuring a trigger -> local-notification-scheduling.md- Calling registerForRemoteNotifications or handling its device-token callbacks -> remote-push-registration.md- Setting UNUserNotificationCenterDelegate, willPresent, or didReceive -> notification-delegate-handling.md- Defining UNNotificationAction/UNTextInputNotificationAction/UNNotificationCategory or setNotificationCategories -> notification-actions-and-categories.md- Removing/inspecting pending or delivered requests, or setting badge count -> managing-pending-delivered-and-badge.mdNever load more than the contracts relevant to the specific question.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/usernotifications/ — do not guess or fall back togeneral knowledge. `UNNotificationServiceExtension`/`UNNotificationContentExtension`rich-media extensions, critical-alert entitlement specifics,location-based triggers (`UNLocationNotificationTrigger`), APNsserver-side payload construction, ActivityKit/Live Activities, andwatchOS-specific notification interfaces are deferred/unbuilt scope —report that explicitly rather than answering from general knowledge (seedocs/architecture/domain-map.md). Notification *design* questions(content wording, timing judgment, foreground UX, badge conventions) areowned by the `human-interface-guidelines` Skill, not this one.

Frequently asked questions