push-notification-setup
Implements push notifications across iOS, Android, and web using Firebase Cloud Messaging and native services. Use when adding notification capabilities, handling background messages, or setting up notification channels.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill push-notification-setup88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, uses natural trigger terms users would actually say, explicitly states both what it does and when to use it, and has a clear distinctive niche around push notifications and Firebase.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'implements push notifications', 'handling background messages', 'setting up notification channels' across specific platforms (iOS, Android, web) using named technology (Firebase Cloud Messaging). | 3 / 3 |
Completeness | Clearly answers both what ('Implements push notifications across iOS, Android, and web using Firebase Cloud Messaging and native services') and when ('Use when adding notification capabilities, handling background messages, or setting up notification channels'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'push notifications', 'notification capabilities', 'background messages', 'notification channels', plus platform names (iOS, Android, web) and technology (Firebase Cloud Messaging). | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on push notifications with specific platform and technology mentions (Firebase, iOS, Android, web). Distinct triggers like 'notification channels' and 'background messages' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples covering three major platforms. The content is appropriately concise and assumes Claude's competence. However, it lacks explicit workflow sequencing (e.g., 'first configure Firebase console, then add dependencies, then implement code') and validation checkpoints for verifying successful setup.
Suggestions
Add a brief workflow sequence at the top outlining the setup order: 1) Configure Firebase/APNs console, 2) Add dependencies, 3) Implement permission request, 4) Verify token received, 5) Test with a sample notification
Include validation steps such as how to verify token registration succeeded and how to test notifications during development
Add references to detailed guides for mentioned but unexplained topics like 'notification channels' and 'deep linking'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only executable code examples without explaining what push notifications are or how Firebase works. Every section delivers actionable code without padding. | 3 / 3 |
Actionability | All code examples are complete and executable across three platforms (React Native, iOS Swift, Android Kotlin). The examples cover the full lifecycle: permission requests, token handling, foreground/background message handling, and token refresh. | 3 / 3 |
Workflow Clarity | While the code examples are clear, there's no explicit workflow sequence for setting up notifications end-to-end. Missing validation steps like verifying token registration succeeded, testing notification delivery, or troubleshooting common failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized by platform with clear headers, but the 'Best Practices' section mentions deep linking and notification channels without references to detailed guides. Could benefit from links to platform-specific setup docs or troubleshooting guides. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.