Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Notification System
v1.0.1Manage outbound notifications across WhatsApp, Telegram, email. Handle templates, scheduling, delivery tracking, rate limiting.
⭐ 0· 98·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The description claims full outbound delivery across WhatsApp, Telegram, and Outlook email, with scheduling, tracking, and rate limiting, but the bundle contains only templates, a pending.json queue, and docs. There are no connector implementations, no code to talk to WhatsApp/Telegram/Office365, and no declared credentials; the SKILL expects external tools (a 'message' CLI and an 'outlook' skill) and scripts that are not provided. The required capabilities (API keys, bot tokens, SMTP/O365 access) are missing from the package and not declared.
Instruction Scope
SKILL.md instructs the agent to run commands and scripts (e.g., message send, outlook send, node notification-system/process-queue.js, and PowerShell helpers) and to read/store queue and log files, but the referenced runtime artifacts are absent. The instructions stay within the notification-system directory, which is appropriate, but they rely on unspecified external tools/skills and on files that the package does not contain (see missing files below). This creates scope ambiguity: the agent may try to locate or invoke arbitrary system tools or other skills to fulfill these steps.
Install Mechanism
No install spec and no shipped executable code reduces installation risk — nothing will be automatically downloaded or executed by an installer. This is an instruction-only skill (low write-to-disk risk).
Credentials
The skill declares no required environment variables or credentials, yet to perform its stated function it would need WhatsApp/Telegram bot tokens and Office365 credentials (or other provider keys). The absence of declared primaryEnv or required env vars is disproportionate to the advertised functionality and is an incoherence that should be resolved before use.
Persistence & Privilege
always is false and there is no indication the skill requests persistent elevated privileges or modifies other skills or system settings. It only references local files under notification-system, which is reasonable.
What to consider before installing
This skill reads like documentation and templates for a notification system rather than a ready-to-run integration. Before installing or using it: 1) Do not run any referenced scripts (node notification-system/process-queue.js, quick-notify.ps1, process-queue.ps1, get-stats.ps1) unless you have reviewed their code — those files are referenced but not included. 2) Expect to supply channel credentials (WhatsApp API/broker, Telegram bot token, Office365/API credentials) — the skill does not declare or request them, so plan secure storage (secrets manager) and never paste keys into untrusted prompts. 3) Verify where sending will actually occur: SKILL.md relies on a 'message' CLI and an 'outlook' skill that are external; confirm those tools exist and are trustworthy. 4) Check missing artifacts the docs reference (process-queue.js, PowerShell scripts, queue/scheduled.json, logs/ delivery files, and a config/ folder) — their absence means the skill is incomplete and an agent might attempt to locate or call other system components. 5) If you need this functionality, obtain a version that includes the connector code or a clear, minimal integration guide for securely configuring connectors and credentials. If you cannot verify these points, treat the package as incomplete and avoid enabling it for autonomous use.Like a lobster shell, security has layers — review code before you run it.
latestvk97527qarpaffw0j93cfz7pn8x84803n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.