LLM NeverDie

Your OpenClaw should never have zero LLMs. NeverDie protects against the silent killer — every model in your fallback chain going down at once. It enforces p...

This skill appears to do what it claims: it deploys a local Node.js monitor that reads OpenClaw logs, writes local state/alert files, and optionally sends brief Telegram alerts to api.telegram.org. Before installing: (1) verify you are comfortable storing the Telegram bot token/chat ID in ~/.openclaw/workspace/.neverdie-config.json (or as env vars); (2) inspect your gateway.err.log contents to ensure no sensitive data will be incidentally read (the monitor does not transmit log contents, but it scans those files); (3) be aware setup.sh will add a cron job entry to ~/.openclaw/cron/jobs.json so the monitor persists and runs even when LLMs are down; remove that entry manually if you uninstall and the automated uninstall fails; (4) review the bundled scripts (fallback-monitor.js and setup.sh) yourself if you want to confirm there are no changes to the alert text or additional network calls — the provided code only contacts api.telegram.org. Note: there are minor robustness bugs in setup/uninstall node -e calls (a bug in passing CRON_FILE in one uninstall path), which look like sloppy scripting rather than malicious behavior. If you accept those tradeoffs, the skill is coherent with its stated purpose.

Type: OpenClaw Skill Name: neverdie Version: 1.2.0 The 'neverdie' skill is a resilience utility designed to monitor OpenClaw for LLM failures and notify users via Telegram. It includes a standalone Node.js monitor (`fallback-monitor.js`) and a setup script (`setup.sh`) that configures a persistent cron job. The code demonstrates good security practices by explicitly avoiding the exfiltration of raw log data or API keys, instead sending only hardcoded alert strings to the external Telegram API. All high-risk behaviors, such as file system access and persistence, are directly aligned with the stated purpose of providing out-of-band monitoring.