Webchat Audio Notifications
v1.2.0Add browser audio notifications to Moltbot/Clawdbot webchat with 5 intensity levels - from whisper to impossible-to-miss (only when tab is backgrounded).
⭐ 1· 2.4k·3 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, SKILL.md install steps, and included files (notification.js, howler, sounds, examples, docs) all match: a client-side webchat audio notifier. No unrelated binaries, env vars, or cloud credentials are requested.
Instruction Scope
Runtime instructions are limited to copying client files into your webchat, loading scripts, initializing the notifier, and hooking into message events. One note: config-loader.js fetches a JSON config from a configurable path (default local path) — if misconfigured to point at an external URL it could pull remote config, so ensure configPath is local/trusted.
Install Mechanism
No automated installer; manual copy of static client files is required. All code is included (Howler is vendored). No downloads from unknown URLs or archive extraction are performed by the skill itself.
Credentials
Skill requires no environment variables, no credentials, and no config paths. It uses browser APIs and localStorage for persisting settings and for storing uploaded custom sounds (base64). These are proportionate to a browser notification feature.
Persistence & Privilege
Skill is not always-enabled, does not request persistent system-wide privileges, and does not modify other skills' configs. It stores settings and optional custom sound data in the browser's localStorage (expected for this feature).
Assessment
This package appears coherent and client-side only, but before installing: 1) host the client files (howler.min.js, notification.js, sounds) on your own webserver—do not reference remote/third-party URLs; 2) review client/notification.js for any unexpected network requests (the code uses fetch only for a configurable local config file by default); 3) note custom sound uploads are stored in localStorage as base64 (size limited and stored per-browser); 4) test in a staging environment to confirm autoplay-handling UX and that no unexpected network traffic occurs; 5) verify licensing (MIT) and the howler.js version for compatibility. If you want extra assurance, run the example pages locally and inspect network traffic in DevTools during tests.Like a lobster shell, security has layers — review code before you run it.
latestvk975mw0apw5cz0yzga30rv915x803m1g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔔 Clawdis