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.
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 strong skill description that clearly identifies the domain (Android push notifications), names specific technologies (FCM, NotificationCompat), and provides an explicit 'Use when' clause with natural trigger terms. It is concise, uses third-person voice, and would be easily distinguishable from other skills in a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: integrating push notifications, using Firebase Cloud Messaging, using NotificationCompat, setting up FCM, creating notification channels, and handling local notifications. | 3 / 3 |
Completeness | Clearly answers both 'what' (integrate push notifications using FCM and NotificationCompat on Android) and 'when' (explicit 'Use when' clause covering setting up FCM, creating notification channels, or handling local notifications). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'push notifications', 'Firebase Cloud Messaging', 'FCM', 'notification channels', 'local notifications', 'NotificationCompat', 'Android'. These cover common variations of how developers would describe notification-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android push notifications via FCM and NotificationCompat. The combination of platform (Android), technology (Firebase Cloud Messaging, NotificationCompat), and task (notification channels, local notifications) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, effectively serving as an overview that points to detailed implementation. Its main weakness is the lack of any executable code examples for core tasks like creating notification channels or setting up FCM services, which limits actionability for a code-heavy topic. The workflow could also benefit from explicit sequencing and validation steps.
Suggestions
Add at least one executable code snippet for the most common task (e.g., creating a NotificationChannel and posting a notification with NotificationCompat)
Include a minimal FirebaseMessagingService code example showing onMessageReceived and onNewToken implementations
Sequence the implementation guidelines as numbered steps (1. Create channel → 2. Request permission → 3. Register service → 4. Handle taps) with a validation note (e.g., 'Verify channel creation by checking NotificationManager.getNotificationChannel()')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bold formatting to highlight key terms without explaining basic Android or Firebase concepts Claude already knows. Every bullet point delivers actionable information without padding. | 3 / 3 |
Actionability | The guidance is specific (naming exact classes, API levels, manifest entries) but lacks any executable code examples. There are no copy-paste ready snippets for creating a NotificationChannel, requesting permissions, or setting up FirebaseMessagingService, which are the core tasks this skill addresses. | 2 / 3 |
Workflow Clarity | The bullet points cover the key steps (channels, permissions, service, flow, payload) but they are presented as unordered guidelines rather than a clear sequence. There are no validation checkpoints or feedback loops for verifying that channels are created correctly or that FCM registration succeeds. | 2 / 3 |
Progressive Disclosure | The SKILL.md serves as a concise overview with a clear one-level-deep reference to implementation details. The structure is well-organized with distinct sections (guidelines, anti-patterns, references) and the reference link is clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.