Agent skill

Notification System

by FerroxLabs in FerroxLabs/wayland

Notification system design expertise covering multi-channel delivery (email, SMS, push, Slack, webhook), template engines, notification preferences and user settings, delivery tracking, retry logic…

Apache-2.0Auto-check passedBackend & APIs

Install Notification System

skills CLI
$ npx skills add FerroxLabs/wayland --skill notification-system -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland notification-system --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/notification-system .claude/skills/notification-system && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
notification-system
GitHub stars
608
Token cost
~3.7k tokens
SKILL.md length
471 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Notification system design expertise covering multi-channel delivery (email, SMS, push, Slack, webhook), template engines, notification preferences and user settings, delivery tracking, retry logic…

  • Works in 10 steps: Always provide unsubscribe: One-click… → Never send without consent: Respect… → Use templates: Consistent branding,… → …
  • The user asks about notification system
  • SKILL.md covers Core Philosophy, Architecture Overview, Multi-Channel Delivery and Template Engine, plus 12 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Notification System is an agent skill from FerroxLabs/wayland. Notification system design expertise covering multi-channel delivery (email, SMS, push, Slack, webhook), template engines, notification preferences and user settings, delivery tracking, retry logic, batching and digest strategies, rate limiting, priority levels, and notification center UI design. Use when the user asks about notification system, notification system best practices, or needs guidance on notification system implementation. Do NOT use when the user needs a different specialized skill or is asking…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Webhooks, Error handling and UI design. It works with Slack. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about notification system
  • Notification system best practices
  • Needs guidance on notification system implementation
  • The user needs a different specialized skill

Example prompts

  • “/notification-system”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Always provide unsubscribe: One-click unsubscribe for email, preference page for others
  2. Never send without consent: Respect opt-in requirements (GDPR, CAN-SPAM)
  3. Use templates: Consistent branding, easier maintenance, localization support
  4. Track deliverability: Monitor bounce rates, complaint rates, open rates
  5. Implement quiet hours: Respect user time zones and sleeping hours
  6. Deduplicate: Prevent sending the same notification twice
  7. Rate limit per user: Prevent notification fatigue
  8. Use digests for non-urgent content: Batch low-priority notifications
  9. Provide fallback channels: If push fails, try email
  10. Log everything: Full audit trail for debugging and compliance

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Notification System loads about 3.7k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 471 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 471 words, ~3,673 tokens.

Download SKILL.mdSave it as .claude/skills/notification-system/SKILL.md (or your agent's skills folder).
name
notification-system
description
Notification system design expertise covering multi-channel delivery (email, SMS, push, Slack, webhook), template engines, notification preferences and user settings, delivery tracking, retry logic, batching and digest strategies, rate limiting, priority levels, and notification center UI design. Use when the user asks about notification system, notification system best practices, or needs guidance on notification system implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
automation shell-scripting guide
metadata.category
software-engineering
metadata.subcategory
developer-tools
metadata.disclaimer
none
metadata.difficulty
intermediate

Notification Automation Builder

Core Philosophy

A notification system is a communication bridge between your application and its users. The best notification systems are user-centric: they deliver the right message, through the right channel, at the right time, with the right urgency level. Over-notification erodes trust and engagement. Under-notification leaves users uninformed. The challenge is finding the balance through user preferences, smart defaults, and delivery intelligence.

Architecture Overview

                    +-------------------+
   Event Source --> | Notification      | --> Channel Router --> Email Provider
   (App events,    | Service           |                    --> SMS Provider
    Webhooks,      | (Priority,        |                    --> Push Provider
    Schedules)     |  Dedup, Batch)    |                    --> Slack/Webhook
                    +-------------------+                    --> In-App Center
                           |
                    +------+------+
                    |             |
              User Prefs    Template Engine
              (Channel,     (Render per
               Quiet hrs,   channel with
               Frequency)   user locale)

Multi-Channel Delivery

Channel Selection Matrix
ChannelLatencyReachRich ContentCostBest For
EmailMinutesHighYes (HTML)LowDetailed info, receipts, reports
SMSSecondsVery HighNo (text only)High2FA, urgent alerts
Push (Mobile)SecondsMediumLimitedFreeReal-time updates, reminders
Push (Web)SecondsLowLimitedFreeRe-engagement, updates
Slack/TeamsSecondsTeam-onlyYes (blocks)FreeTeam notifications, alerts
WebhookSecondsDevelopersJSONFreeIntegrations, automation
In-AppInstantActive usersYesFreeNon-urgent updates, activity
Email Delivery
typescript
// services/channels/email.ts
import { SES } from '@aws-sdk/client-ses';

interface EmailNotification {
    to: string;
    subject: string;
    htmlBody: string;
    textBody: string;
    replyTo?: string;
    tags?: Record<string, string>;
}

class EmailChannel {
    private ses: SES;
# ... (condensed) ...
        });

        return { messageId: result.MessageId! };
    }
}
SMS Delivery
typescript
// services/channels/sms.ts
import twilio from 'twilio';

class SMSChannel {
    private client: twilio.Twilio;

    constructor() {
        this.client = twilio(ENV_CONFIG_VALUE, ENV_CONFIG_VALUE);
    }

    async send(to: string, message: string): Promise<{ messageId: string }> {
        // SMS messages must be concise (160 chars for single segment)
        const truncated = message.length > 160
            ? message.substring(0, 157) + '...'
            # ... (condensed) ...
        });

        return { messageId: result.sid };
    }
}
Push Notifications
typescript
// services/channels/push.ts
import * as admin from 'firebase-admin';

class PushChannel {
    private messaging: admin.messaging.Messaging;

    constructor() {
        admin.initializeApp({ credential: admin.credential.applicationDefault() });
        this.messaging = admin.messaging();
    }

    async send(deviceToken: string, notification: {
        title: string;
        body: string;
        # ... (condensed) ...
            notification,
        });
        return { messageId: result };
    }
}
Webhook Delivery
typescript
// services/channels/webhook.ts
class WebhookChannel {
    async send(url: string, payload: any, options: {
        secret?: string;
        timeout?: number;
        retries?: number;
    } = {}): Promise<{ statusCode: number; responseTime: number }> {
        const body = JSON.stringify(payload);
        const headers: Record<string, string> = {
            'Content-Type': 'application/json',
            'User-Agent': 'MyApp-Webhook/1.0',
        };

        // Sign payload with HMAC for verification
        # ... (condensed) ...
            statusCode: response.status,
            responseTime: Date.now() - start,
        };
    }
}

Template Engine

typescript
// services/templates/engine.ts
import Handlebars from 'handlebars';

interface NotificationTemplate {
    id: string;
    channels: {
        email?: { subject: string; html: string; text: string };
        sms?: { body: string };
        push?: { title: string; body: string };
        slack?: { blocks: any[] };
    };
}

class TemplateEngine {
    # ... (condensed) ...
            title: 'Order Confirmed',
            body: 'Your order #{{orderId}} (${{total}}) is confirmed!',
        },
    },
});

Notification Preferences

typescript
// models/notificationPreferences.ts
interface NotificationPreferences {
    userId: string;
    channels: {
        email: boolean;
        sms: boolean;
        push: boolean;
        inApp: boolean;
    };
    categories: {
        [category: string]: {
            enabled: boolean;
            channels?: string[];  // Supersede default channels
            frequency?: 'immediate' | 'hourly_digest' | 'daily_digest';
        # ... (condensed) ...
        'social': { enabled: true, frequency: 'immediate' },
    },
    quietHours: { enabled: false, start: '22:00', end: '08:00', timezone: 'America/New_York' },
    unsubscribedAll: false,
};
Preference Enforcement
typescript
class NotificationRouter {
    async route(notification: Notification, userId: string): Promise<string[]> {
        const prefs = await this.getPreferences(userId);

        // Global unsubscribe check (except mandatory categories)
        if (prefs.unsubscribedAll && !notification.mandatory) {
            return [];
        }

        // Category check
        const categoryPref = prefs.categories[notification.category];
        if (categoryPref && !categoryPref.enabled && !notification.mandatory) {
            return [];
        }
# ... (condensed) ...
            // Crosses midnight (e.g., 22:00 - 08:00)
            return now >= start || now < end;
        }
    }
}

Delivery Tracking

typescript
// models/deliveryLog.ts
interface DeliveryLog {
    id: string;
    notificationId: string;
    userId: string;
    channel: string;
    status: 'pending' | 'sent' | 'delivered' | 'failed' | 'bounced' | 'clicked' | 'read';
    providerMessageId?: string;
    error?: string;
    attempts: number;
    sentAt?: Date;
    deliveredAt?: Date;
    readAt?: Date;
    metadata?: Record<string, any>;
# ... (condensed) ...
            error,
            attempts: log.attempts + 1,
        });
    }
}

Retry Logic

typescript
class NotificationRetryHandler {
    private readonly maxRetries = 3;
    private readonly retryDelays = [60, 300, 900]; // 1min, 5min, 15min

    async handleFailure(delivery: DeliveryLog): Promise<void> {
        if (delivery.attempts >= this.maxRetries) {
            await this.markPermanentFailure(delivery);
            return;
        }

        const delay = this.retryDelays[delivery.attempts] || 900;

        // Determine if error is retryable
        if (this.isRetryable(delivery.error)) {
            # ... (condensed) ...
        if (fallback) {
            await this.resendViaChannel(delivery.notificationId, delivery.userId, fallback);
        }
    }
}

Batching and Digest

typescript
class DigestService {
    /**
     * Instead of sending 50 individual notifications,
     * batch them into a single digest email.
     */
    async processDigest(userId: string, frequency: 'hourly' | 'daily'): Promise<void> {
        const cutoff = frequency === 'hourly'
            ? new Date(Date.now() - 3600000)
            : new Date(Date.now() - 86400000);

        const pending = await db.notifications.findPending(userId, cutoff);

        if (pending.length === 0) return;

        # ... (condensed) ...
            (groups[n.category] = groups[n.category] || []).push(n);
            return groups;
        }, {} as Record<string, Notification[]>);
    }
}

Rate Limiting

typescript
class NotificationRateLimiter {
    // Limits per channel per user
    private limits: Record<string, { max: number; windowMs: number }> = {
        email: { max: 10, windowMs: 3600000 },     // 10 per hour
        sms: { max: 5, windowMs: 3600000 },         // 5 per hour
        push: { max: 20, windowMs: 3600000 },        // 20 per hour
        slack: { max: 30, windowMs: 3600000 },        // 30 per hour
    };

    async isAllowed(userId: string, channel: string): Promise<boolean> {
        const limit = this.limits[channel];
        if (!limit) return true;

        const key = `notif_rate:${userId}:${channel}`;
        # ... (condensed) ...
        }

        return count <= limit.max;
    }
}

Priority Levels

typescript
enum NotificationPriority {
    LOW = 'low',           // In-app only, can be batched
    NORMAL = 'normal',     // Default channels, respects quiet hours
    HIGH = 'high',         // All enabled channels, respects quiet hours
    URGENT = 'urgent',     // All channels, ignores quiet hours, no batching
    CRITICAL = 'critical', // All channels + SMS, ignores all preferences
}

function getPriorityBehavior(priority: NotificationPriority) {
    return {
        low:      { respectQuietHours: true,  batchable: true,  fallbackChannel: false },
        normal:   { respectQuietHours: true,  batchable: true,  fallbackChannel: false },
        high:     { respectQuietHours: true,  batchable: false, fallbackChannel: true  },
        urgent:   { respectQuietHours: false, batchable: false, fallbackChannel: true  },
        critical: { respectQuietHours: false, batchable: false, fallbackChannel: true  },
    }[priority];
}

Notification Center (In-App)

API Design
typescript
// GET /api/notifications?page=1&per_page=20&unread_only=false
interface NotificationCenterResponse {
    items: NotificationItem[];
    total: number;
    unread_count: number;
    page: number;
}

interface NotificationItem {
    id: string;
    title: string;
    body: string;
    category: string;
    priority: string;
    # ... (condensed) ...
}

// PATCH /api/notifications/:id/read
// POST /api/notifications/mark-all-read
// DELETE /api/notifications/:id
Real-Time Updates
typescript
// WebSocket or Server-Sent Events for real-time notification delivery
// Server-Sent Events (simpler, one-directional)
app.get('/api/notifications/stream', (req, res) => {
    res.writeHead(200, {
        'Content-Type': 'text/event-stream',
        'Cache-Control': 'no-cache',
        'Connection': 'keep-alive',
    });

    const userId = req.user.id;

    const handler = (notification: NotificationItem) => {
        res.write(`data: ${JSON.stringify(notification)}\n\n`);
    };

    notificationBus.subscribe(userId, handler);

    req.on('close', () => {
        notificationBus.unsubscribe(userId, handler);
    });
});

Best Practices

  1. Always provide unsubscribe: One-click unsubscribe for email, preference page for others
  2. Never send without consent: Respect opt-in requirements (GDPR, CAN-SPAM)
  3. Use templates: Consistent branding, easier maintenance, localization support
  4. Track deliverability: Monitor bounce rates, complaint rates, open rates
  5. Implement quiet hours: Respect user time zones and sleeping hours
  6. Deduplicate: Prevent sending the same notification twice
  7. Rate limit per user: Prevent notification fatigue
  8. Use digests for non-urgent content: Batch low-priority notifications
  9. Provide fallback channels: If push fails, try email
  10. Log everything: Full audit trail for debugging and compliance
Show full SKILL.md (198 more words)Show less

When to Use

Use this skill when:

  • Designing or implementing notification system solutions
  • Reviewing or improving existing notification system approaches
  • Making architectural or implementation decisions about notification system
  • Learning notification system patterns and best practices
  • Troubleshooting notification system-related issues

Do NOT use this skill when:

  • The question is about a fundamentally different technology domain
  • A more specific sibling skill covers the exact topic needed
  • The user needs a complete hands-on tutorial rather than expert guidance

Output Format

markdown
# Notification System Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]

Example

Input: "Help me implement notification system for a medium-scale production application"

Output: A structured analysis covering current state assessment, recommended notification system approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.

Edge Cases

  • Legacy system integration: When notification system must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
  • Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
  • Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
  • Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/software-engineering/notification-system of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Notification System next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Notification System compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Notification System this skillFerroxLabs/wayland608—~3.7kAutomated safety check: PassApache-2.0
API Integration Specialistaiskillstore/marketplace4302 repos~2.2kAutomated safety check: PassNone
Email Best Practicesviclafouch/meme-studio1107 repos~787Automated safety check: PassNone
API Route Patternsbybren-llc/safe-agentic-workflow421—~1.6kAutomated safety check: PassMIT
Rails Security Multitenancymarckohlbrugge/37signals-skills724—~1.7kAutomated safety check: PassNone
Frappe Core APIImpertio-Studio/Frappe_Claude_Skill_Package1871 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • API Integration Specialist

    aiskillstore/marketplace

    Expert in integrating third-party APIs with proper authentication, error handling, rate limiting, and retry logic.

    430 GitHub starsUsed in 2 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • Email Best Practices

    viclafouch/meme-studio

    A skill your agent uses when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM…

    110 GitHub starsUsed in 7 repos~787 tokens
    Backend & APIsAuto-check passed
  • API Route Patterns

    bybren-llc/safe-agentic-workflow

    API route implementation patterns with RLS, validation, and error handling. Use when creating API routes, implementing CRUD endpoints, adding server-side…

    421 GitHub stars~1.6k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed
  • Rails Security Multitenancy

    marckohlbrugge/37signals-skills

    Apply Rails security and multi-tenant safety practices including scoped queries, SSRF defenses, rate limiting, and tenant-scoped realtime updates.

    724 GitHub stars~1.7k tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed
  • Frappe Core API

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when building ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting.

    187 GitHub starsUsed in 1 repo~3.2k tokens
    Backend & APIsAuto-check passed
  • Channel Debug Core

    vercel-labs/vercel-openclaw-archived

    Official

    Channel webhook triage for vercel-openclaw Slack/Telegram/Discord/WhatsApp issues: prove deployment state, collect admin readiness endpoints, build evidence-first handoff before fixes.

    117 GitHub stars~2k tokensUpdated 4 mo ago
    Backend & APIsAuto-check: notes

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Notification System

What does Notification System do?

Notification system design expertise covering multi-channel delivery (email, SMS, push, Slack, webhook), template engines, notification preferences and user settings, delivery tracking, retry logic…. Notification System is an agent skill from FerroxLabs/wayland. Notification system design expertise covering multi-channel delivery (email, SMS, push, Slack, webhook), template engines, notification preferences and user settings, delivery tracking, retry logic, batching and digest strategies, rate limiting, priority levels, and notification center UI design.

When should I use Notification System?

Notification System fits situations like: the user asks about notification system; notification system best practices; needs guidance on notification system implementation; the user needs a different specialized skill.

How do I install Notification System in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill notification-system -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/software-engineering/notification-system in FerroxLabs/wayland) into .claude/skills/notification-system in your project. Claude Code loads it when a task matches its description.

How do I install Notification System in Codex?

Run `npx skills add FerroxLabs/wayland --skill notification-system -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/software-engineering/notification-system in FerroxLabs/wayland) into .agents/skills/notification-system in your project. Codex loads it when a task matches its description.

Can I use Notification System in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill notification-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notification-system, .gemini/skills/notification-system, .github/skills/notification-system and .opencode/skills/notification-system in your project.

What does Notification System need to run?

SKILL.md names no scripts, command-line tools or credentials: Notification System is instructions for the agent only.

Does Notification System access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Notification System safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Notification System use?

Notification System is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Notification System use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Notification System?

Skills that share tags, products or a category with Notification System: API Integration Specialist (aiskillstore/marketplace, 430 stars), Email Best Practices (viclafouch/meme-studio, 110 stars), API Route Patterns (bybren-llc/safe-agentic-workflow, 421 stars) and Rails Security Multitenancy (marckohlbrugge/37signals-skills, 724 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Notification System?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.