Integrates web push notifications into Angular applications using Firebase Cloud Messaging and service workers.
- GitHub stars
- 171
- Files
- 1
- Last commit
- Oct 15, 2026
- License
- MIT
- Allowed tools
- —
What does the cometchat-angular-v5-push skill do?
cometchat-angular-v5-push integrates web push notifications into Angular applications using Firebase Cloud Messaging and service workers.
Summary generated from the skill's SKILL.md.
About the cometchat-angular-v5-push skill
Developers building Angular applications that require background messaging can use this skill to integrate web push notifications. It facilitates the connection between the CometChat Notifications product and Firebase Cloud Messaging to ensure users receive alerts even when the application is closed or backgrounded. The skill focuses on managing the token lifecycle, including registering the FCM token after a successful login and unregistering it during logout to prevent cross-user notification errors.
Because push notification requirements change frequently, this skill operates as a docs-first tool rather than providing a static code recipe. It relies on fetching the most current documentation via the cometchat-angular-v5-core reference map to ensure accuracy regarding payload shapes and provider setup. Users must ensure a service worker is served from the origin root and that permission requests are triggered by user gestures to comply with browser security rules. This tool is designed for use with Angular versions 17 through 21 and requires the CometChat Notifications product to be enabled in the dashboard.
What an agent can do with it
- 1Enable background notificationsConfigure an Angular app to notify users when the application is closed or running in the background.
- 2Manage FCM token lifecycleImplement logic to register the Firebase Cloud Messaging token after login and remove it upon logout.
- 3Handle iOS Safari requirementsGuide users to install the site as a PWA to enable web push functionality on iOS devices.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the cometchat-angular-v5-push skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the cometchat-angular-v5-push skill in Plugin
/plugin marketplace add cometchat/cometchat-skills /plugin install cometchat-skills@cometchat
Install the cometchat-angular-v5-push skill in Claude Code
~/.claude/skills/cometchat-angular-v5-push/SKILL.md
$ npx degit cometchat/cometchat-skills/skills/cometchat-angular-v5-push ~/.claude/skills/cometchat-angular-v5-pushInstall the cometchat-angular-v5-push skill in Claude Code (project)
.claude/skills/cometchat-angular-v5-push/SKILL.md
$ npx degit cometchat/cometchat-skills/skills/cometchat-angular-v5-push .claude/skills/cometchat-angular-v5-pushInstall the cometchat-angular-v5-push skill in Codex
~/.agents/skills/cometchat-angular-v5-push/SKILL.md
$ npx degit cometchat/cometchat-skills/skills/cometchat-angular-v5-push ~/.agents/skills/cometchat-angular-v5-pushInstall the cometchat-angular-v5-push skill in Gemini CLI
~/.gemini/skills/cometchat-angular-v5-push/SKILL.md
$ npx degit cometchat/cometchat-skills/skills/cometchat-angular-v5-push ~/.gemini/skills/cometchat-angular-v5-pushInstall the cometchat-angular-v5-push skill in Claude.ai
npx degit cometchat/cometchat-skills/skills/cometchat-angular-v5-push cometchat-angular-v5-push && zip -r cometchat-angular-v5-push.zip cometchat-angular-v5-push # claude.ai → Customize → Skills → + → Create skill → Upload a skill → cometchat-angular-v5-push.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablecometchat/cometchat-skills/skills/cometchat-angular-v5-push is public and reachablegithub.com/cometchat/cometchat-skills/tree/HEAD/skills/comet ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-15github.com/cometchat/cometchat-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/cometchat/cometchat-skills/blob/HEAD/skills/comet ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/cometchat/cometchat-skills/blob/HEAD/skills/comet ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/cometchat/cometchat-skills/blob/HEAD/skills/comet ↗Finding
SKILL.md
View on GitHubGround truth: push is the CometChat Notifications product, not a UI Kit component — this skill is THIN and docs-first. Registration, payload shape and provider setup are FETCHED from the notifications docs via
cometchat-angular-v5-core/references/docs-map.md; nothing about them is baked here. Live delivery cannot be auto-smoked — say so honestly rather than claiming verification.
Companion skills (read first)
cometchat-angular-v5-core— install, credentials,init→login→render. Assumed.
Use this skill when
Delivering notifications while the app is closed or backgrounded.
This skill is deliberately THIN — fetch the docs
Push spans a product (CometChat Notifications), a third-party provider (Firebase/FCM), a service worker, and browser permission rules. Every one of those changes independently, so a baked recipe goes stale fast.
Start here: {SDK_DOCS_BASE}/notifications/overview.md, then the web push integration page. Discover the current pages from the SDK index (cometchat-angular-v5-core/references/docs-map.md). Read before writing.
Angular's own docs cover push only inside {DOCS_BASE}/ui-kit/angular/campaigns.md — there is no dedicated Angular push page. That is a known docs gap; the product-level notifications docs are the source of truth.
What is true regardless of version
1. Push is a separate product. It must be enabled and configured for the app in the dashboard, with provider credentials added there. No client code substitutes for that step.
2. It is not the UI Kit. Registration is SDK-level (CometChatNotifications), not a component. There is nothing to render.
3. It needs a service worker at origin root. firebase-messaging-sw.js must be served from /, not from a nested path. In Angular, add it to the app's assets in angular.json so it lands at the root of dist/, and confirm it is reachable at /firebase-messaging-sw.js after build — a 404 there is the single most common cause of "push does nothing".
4. Permission requires a user gesture. Call the permission request from a click. Browsers block it on load, and repeated silent blocks poison the origin.
5. Token lifecycle is yours. Register the FCM token after login; unregister on logout. Skipping the unregister sends the next user's notifications to the previous device.
6. iOS Safari is PWA-only. Web push on iOS requires the site installed to the home screen. Not a bug; set expectations.
Angular specifics
- Register the token after
login()resolves — see core's guarded-login pattern. - Put registration in a service, not a component, so it does not re-run per route.
- If the app is SSR, guard all of it with
isPlatformBrowser(cometchat-angular-v5-patterns). - Unregister in the same place you call
CometChatUIKit.logout().
Verify it works
Push cannot be verified in a headless browser: it needs a real device or browser profile, a live provider, and a backgrounded app. Expect to test by hand:
- Load over HTTPS, grant permission from a click.
- Confirm
/firebase-messaging-sw.jsreturns 200. - Background the tab; send a message from a second account.
- Notification arrives; tapping it focuses the app.
- Log out; confirm notifications stop.
Common pitfalls
- Notifications not enabled in the dashboard — nothing works, no error.
- Service worker not at origin root — silent failure.
- Permission requested on load — blocked.
- Token registered before login — no user to attach it to.
- No unregister on logout — notifications follow the wrong user.
- Expecting iOS Safari to work outside a PWA.
- Baking a recipe from memory — fetch the docs; this area moves.
Files in this skill
1cometchat-angular-v5-push skill questions
How do I install the cometchat-angular-v5-push skill in Claude Code?
Run npx degit cometchat/cometchat-skills/skills/cometchat-angular-v5-push ~/.claude/skills/cometchat-angular-v5-push. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the cometchat-angular-v5-push skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
Does this skill include UI components for notifications?
No, push notifications are a separate product and registration happens at the SDK level rather than through a UI Kit component.
Where should the service worker be located in an Angular project?
The service worker must be served from the origin root. In Angular, you should add it to the app's assets in angular.json so it lands at the root of dist/.
How can I get web push to work on iOS Safari?
Web push on iOS requires the website to be installed as a Progressive Web App (PWA) to the home screen.