CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 tight, code-first skill body that respects the token budget and gives executable per-platform examples. The main gaps are the absence of an ordered setup workflow with validation checkpoints (project configuration steps, device testing verification) and minor incompleteness in the code examples (undefined helper functions, missing Android 13+ permission and channel setup).

Suggestions

Add a brief ordered workflow section (1. configure Firebase project, 2. register the platform, 3. request permission and register token, 4. verify on a real device) with explicit validation checkpoints such as confirming the token arrives at the server and that a test notification displays in both foreground and background states.

Complete the code examples: define or explicitly flag the placeholder helpers (sendTokenToServer, showLocalNotification), and for Android add notification-channel creation and the POST_NOTIFICATIONS runtime permission check required on Android 13+.

Consider moving platform-specific setup detail (AndroidManifest service registration, APNs entitlements, deep-link handling) into a references/ file and linking it, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows — it opens with a single sentence and goes straight to executable snippets per platform ("import messaging from '@react-native-firebase/messaging'", "UNUserNotificationCenter.current().requestAuthorization", "NotificationCompat.Builder"), with only terse, functional code comments. Every section earns its tokens; not the 4 anchor because there is no over-explanation to trim.

5 / 5

Actionability

Each platform section provides real, mostly copy-paste-ready code (permission request, token registration, foreground/background handlers, notification builder). It stops short of the 5 anchor because key helpers are undefined placeholders ("sendTokenToServer(token)", "showLocalNotification(message)") and the Android snippet omits notification-channel creation and POST_NOTIFICATIONS permission handling; above the 3 anchor because the code is genuinely executable, not pseudocode.

4 / 5

Workflow Clarity

The content is organized per platform with an implicit sequence inside each snippet (request permission → register → handle messages), but there is no explicit end-to-end workflow: project setup steps (Firebase config, AndroidManifest service registration, APNs entitlements) are absent and the "Best Practices" bullets ("Test on real devices", "Implement deep linking") have no validation checkpoints. Not the 2 anchor because the per-platform sequences are coherent and clearly separated, but the missing checkpoints hold it at the 3 anchor.

3 / 5

Progressive Disclosure

The body (~90 lines) is well-sectioned per platform with clear headers ("## Firebase Cloud Messaging (React Native)", "## iOS Native (Swift)", "## Android (Kotlin)", "## Best Practices") and no monolithic wall of text or nested references. It sits below the 5 anchor because at this length, platform-specific detail like the Android channel setup and deep linking arguably belongs in reference files, and no external references are provided at all; above the 3 anchor because everything present is appropriately placed and navigable.

4 / 5

Total

16

/

20

Passed

Description

87%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 description: third person, concrete, and equipped with an explicit 'Use when' clause covering the main trigger scenarios. The only weakness is that a few natural synonyms (FCM, APNs, notification tokens) live only in the metadata keywords rather than the description text itself.

DimensionReasoningScore

Specificity

"Implements push notifications across iOS, Android, and web using Firebase Cloud Messaging and native services" names concrete platforms and technologies, with the trigger clause adding further concrete capability areas ("handling background messages", "setting up notification channels"). It falls just below the 5 anchor because it doesn't enumerate as many distinct concrete actions as the comprehensive example (e.g., token registration, permission handling are only implied), but it clearly exceeds the 1-2-action scope of anchor 3.

4 / 5

Completeness

The description explicitly answers both questions: 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, matching the 5 anchor. Not the 4 anchor because the 'when' clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Natural phrases like "push notifications", "adding notification capabilities", "handling background messages", and "notification channels" match what users would actually say. It misses a few common synonyms in the description itself ("FCM"/"Firebase", "APNs", "notification tokens"), keeping it below the 5 anchor's comprehensive synonym coverage, though these do appear in the metadata keywords.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (cross-platform push notifications via FCM/native services) with distinct trigger phrases unlikely to fire for unrelated skills. It's at least as distinctive as the 5 anchor's PDF example, and there's no generic overlap with other skill domains.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.