android-notifications

Integrate Android app notifications using Firebase Cloud Messaging and NotificationCompat. Use when setting up FCM, notification channels, or client-side notification taps; defer Flutter, server sends, WorkManager orchestration, and generic Intent handling.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-3

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

A tight, actionable overview that delegates executable code to a well-structured one-level reference, achieving strong conciseness and progressive disclosure. The main gap is workflow clarity: the body organizes by topic rather than presenting an explicit, validated setup sequence.

Suggestions

Add a short ordered setup sequence (build config -> service -> manifest -> channel -> permission -> tap handling) with a validation checkpoint (e.g., verify the channel exists before notify, confirm POST_NOTIFICATIONS granted before posting) to lift workflow clarity.

Remove or fill the empty "Priority: P2 (MEDIUM)" section so no header is content-free.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse bullets naming exact APIs and version gates with no explanation of concepts Claude already knows; every line earns its place, though the empty "Priority: P2" header is minor overhead.	3 / 3
Actionability	Concrete, specific directives name exact APIs and thresholds (NotificationChannel on API 26+, POST_NOTIFICATIONS on API 33, FirebaseMessagingService with onMessageReceived/onNewToken, MESSAGING_EVENT manifest action); executable Kotlin lives one level deep in the referenced file, which the rubric does not penalize for instruction-only skills.	3 / 3
Workflow Clarity	Content is organized by concern (Channels, Permissions, Service, Flow, Payload) but the body lacks an explicit ordered sequence and any validation checkpoints; the actual numbered 1-6 sequence lives only in the reference file.	2 / 3
Progressive Disclosure	A concise overview body points to a single, clearly-signaled one-level-deep reference ([Implementation Details](references/implementation.md)), which exists and is well-organized into numbered sections, giving easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 well-constructed description with explicit trigger guidance and strong boundary-setting via the defer clause. It is slightly held back by a single integrated action verb rather than a list of concrete capabilities and by the omission of the common term "push notifications."

Suggestions

List multiple discrete concrete actions (e.g., create notification channels, request POST_NOTIFICATIONS, handle taps) rather than the single verb "Integrate" to raise specificity.

Add the common user term "push notifications" alongside FCM so the trigger phrasing matches what users naturally say.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete technologies ("Firebase Cloud Messaging and NotificationCompat") but frames a single integrated action rather than listing multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	Explicitly states what it does ("Integrate Android app notifications using Firebase Cloud Messaging and NotificationCompat") and when to use it via a clear "Use when..." clause, satisfying both what and when.	3 / 3
Trigger Term Quality	"Use when setting up FCM, notification channels, or client-side notification taps" provides relevant trigger terms but omits the most common user phrasing "push notifications," missing common variations.	2 / 3
Distinctiveness Conflict Risk	The explicit deferral clause ("defer Flutter, server sends, WorkManager orchestration, and generic Intent handling") carves a clear niche and sharply reduces conflict with adjacent skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/android/android-notifications/SKILL.md
Commit: 9f695e8

Reviewed: 6 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.