android-notifications

Integrate push notifications using Firebase Cloud Messaging and NotificationCompat on Android. Use when setting up FCM, creating notification channels, or handling local notifications.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A well-organized, token-efficient overview that appropriately delegates executable detail to a single real reference file. Its weakness is actionability and workflow clarity: the body describes APIs and constraints without inline executable examples and without explicit validation/feedback checkpoints for the multi-step notification setup.

Suggestions

Add a short inline code snippet for at least the channel-creation and permission-request steps (or a copy-paste-ready skeleton) so the body is executable, not just descriptive.

Add an explicit validation checkpoint to the flow — e.g., 'After registering the channel, verify via NotificationManager.getNotificationChannel; after requesting permission, confirm grant status before sending' — with a fix-retry note, lifting workflow clarity.

The Anti-Patterns section restates guidelines as negatives ('No Missing Channel'); consider tightening or merging to avoid redundant tokens with the Implementation Guidelines.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse guideline bullets naming the APIs and platform constraints ('Create NotificationChannel with unique ID (required for API 26+)', 'Explicitly request POST_NOTIFICATIONS on Android 13+ (API 33)') with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.	3 / 3
Actionability	Guidance names concrete APIs and constraints but the body itself contains no executable code or commands — the runnable Kotlin/XML lives in the referenced implementation.md. Per scoring_notes for code skills, code should be executable; here the inline guidance describes rather than instructs at copy-paste level, so it sits at 'some concrete guidance but incomplete' rather than 3.	2 / 3
Workflow Clarity	Implementation areas are listed (Channels, Permissions, Service, Flow, Payload) giving a recognizable sequence, but there are no explicit validation checkpoints or verify-fix-retry feedback loops for the notification pipeline. The guidelines note missing validation in fragile multi-step operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is a concise overview with one clearly-signaled, one-level-deep reference to a verified real file ([Implementation Details](references/implementation.md)); content is appropriately split with easy navigation, matching the level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Description

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.

A strong, specific description that names concrete capabilities (FCM, NotificationCompat, channels, local notifications) and provides an explicit 'Use when' clause covering what and when. Trigger terms are natural and the scope is well-distinguished from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to specific APIs: 'Integrate push notifications using Firebase Cloud Messaging and NotificationCompat', 'creating notification channels', 'handling local notifications' — comprehensive and concrete, not the level-2 single-domain 'Processes PDF files and extracts content' style.	3 / 3
Completeness	Explicitly answers both: what it does ('Integrate push notifications using FCM and NotificationCompat') and when to use it ('Use when setting up FCM, creating notification channels, or handling local notifications'), the level-3 anchor pattern.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered ('push notifications', 'FCM', 'notification channels', 'local notifications') alongside API names a developer would actually mention, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Android push notifications with distinct, niche triggers (FCM, NotificationCompat, channels) unlikely to overlap with unrelated skills.	3 / 3
	Total	12 / 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
Commit: 611f52a

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.