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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized set of executable cross-platform push-notification code examples that earns high marks for token efficiency and structure. Its weaknesses are undefined helper stubs in the code and the absence of an explicit sequenced workflow with validation checkpoints.

Suggestions

Define or note the contract for the helper stubs (sendTokenToServer, showLocalNotification, showNotification) so the examples are fully self-contained.

Replace vague Best Practices bullets (e.g. "Request permission at appropriate time") with concrete, sequenced steps including a validation checkpoint such as verifying the token was successfully registered server-side.

Add a brief end-to-end ordering (configure platform -> request permission -> register token -> wire message handlers) so the per-platform snippets form one coherent workflow rather than three parallel fragments.

Dimension	Reasoning	Score
Conciseness	Lean, token-efficient body with minimal prose and only purposeful inline comments ("Request permission", "Handle foreground messages"); it does not explain concepts Claude already knows and every line earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready code in three languages covering the common permission/token/handler cases, but helper stubs like sendTokenToServer, showLocalNotification, and showNotification are referenced without implementation, leaving minor gaps short of a 5.	4 / 5
Workflow Clarity	Each platform section implies a rough sequence (permission -> token -> handlers), but there is no explicit multi-step workflow with validation checkpoints or feedback loops, and the Best Practices bullets are vague ("Request permission at appropriate time").	3 / 5
Progressive Disclosure	Under 50 lines of actual content with no need for external references, organized into clear per-platform sections; per the simple-skill guidance this qualifies for the top score on organization alone.	5 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly defines its cross-platform push-notification niche and gives explicit use-when triggers with good keyword coverage. The only minor weakness is a slightly generic action verb ("adding notification capabilities") among otherwise concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions across three platforms ("Implements push notifications across iOS, Android, and web", "handling background messages", "setting up notification channels"), but "adding notification capabilities" is somewhat generic, leaving minor coverage gaps short of a 5.	4 / 5
Completeness	Explicitly states 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") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural keyword coverage including synonyms ("FCM" / "Firebase Cloud Messaging"), platform terms, and user-facing phrases like "notification capabilities" and "background messages".	5 / 5
Distinctiveness Conflict Risk	Clear niche focused on push notifications / FCM with distinct platform-specific triggers, creating minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/push-notification-setup/skills/push-notification-setup/SKILL.md
Commit: 84802a4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.