Notification Hub

Unified notification hub collecting all skill alerts and delivering by priority

This skill appears to do what it says (aggregate events and send notifications), but before installing: 1) Verify how Discord delivery is configured — where is the bot token or webhook stored? The skill mentions TOOLS.md and a channel ID but does not declare required credentials. 2) Confirm the agent's file permissions: the skill reads events/ and writes memory/notifications/; ensure those directories don't contain sensitive secrets you don't want aggregated or transmitted. 3) Prefer explicit credential handling: require a specific env var (e.g., DISCORD_TOKEN or DISCORD_WEBHOOK) and document where TOOLS.md lives and who can edit it. 4) Test in a sandboxed agent or with a throwaway Discord channel to confirm behavior. 5) If you cannot confirm where channel IDs and tokens are stored, treat the skill as risky and do not enable it for agents with access to sensitive data.

Type: OpenClaw Skill Name: mupeng-notification-hub Version: 1.0.0 The skill bundle defines a 'notification-hub' that collects event files from `events/`, classifies them by priority, prevents duplicates using history stored in `memory/notifications/`, and delivers them via Discord DMs or internal queues. While it involves local file system access (read/write) and external network communication (Discord DMs), these capabilities are directly aligned with the stated purpose of a notification hub. There is no evidence of data exfiltration beyond notification content, malicious execution, persistence mechanisms, or prompt injection attempts against the agent to perform unauthorized actions. The JavaScript snippets are illustrative of the intended logic, and the usage examples guide the agent to manage notifications as expected.