Claw Sos

Install, run, and manage the SOS emergency recovery tool for OpenClaw instances. Use when (1) the bot stops responding on Telegram/Discord and needs diagnosi...

Security Scan

The skill's code, instructions, and required access are consistent with an emergency recovery tool for OpenClaw; nothing in the bundle indicates hidden exfiltration or unrelated credential requests, though normal operational risks (running recovery operations as root, curl|bash install) apply.

Purpose & Capability

Name/description (SOS emergency recovery for OpenClaw) align with the included scripts: sos.sh implements diagnostics, restart/kill/rollback, network checks, Telegram test, and logging; install/uninstall scripts match the expected need to place a helper binary in /usr/local/bin. No unrelated credentials or unrelated platform APIs are requested.

Instruction Scope

SKILL.md and sos.sh stay within recovery scope: they read the OpenClaw config (openclaw.json), inspect processes, logs, services (systemd/launchctl), run network checks (DNS/HTTP), and optionally send a Telegram test using the already-configured bot token. The instructions do ask the operator to scp/ssh as root for remote installs and to run potentially destructive actions (force kill / nuclear), which is appropriate for an emergency tool but requires explicit user consent when performed.

Install Mechanism

No packaged install spec in registry; install.sh offers installing by copying the bundled script or via curl to a raw.githubusercontent.com URL (GitHub raw). Using GitHub raw is a known release host (reasonable), but piping raw install scripts to bash (curl | bash) is inherently riskier — standard caution applies. No downloads from obscure hosts or shorteners were observed.

Credentials

The skill declares no required env vars and does not request external secrets. The script reads OPENCLAW_HOME (optional) and openclaw.json to access the existing OpenClaw configuration (including the bot token already configured there) in order to run Telegram tests; this is proportional to its stated purpose. The script requires privileged operations (systemctl, killing processes) which is expected for a recovery tool.

Persistence & Privilege

always:false and user-invocable:true. The skill does write logs to ~/.openclaw/backups/sos.log and may start/stop services or run node to start a gateway — actions appropriate for recovery. It does not request to persist as a platform-wide skill or modify other skills' configs.

Assessment

This skill appears to do what it says: an on-host emergency recovery helper for OpenClaw. Before installing or running it, consider: (1) Review openclaw.json — the script will read your OpenClaw config (including any bot token) to run Telegram tests; ensure you trust local config usage. (2) The installer offers a curl|bash option; prefer copying the provided sos.sh and inspecting it yourself rather than piping remote code directly into a shell. (3) Recovery actions (force kill, nuclear) are destructive by design — run them only when you understand the consequences and have backups (sos logs and config backups are stored at ~/.openclaw/backups/). (4) The script needs privileges to manage services and kill processes; run as an authorized administrator and audit activity in ~/.openclaw/backups/sos.log. If you want greater assurance, inspect the full sos.sh contents (you have them in the bundle) to confirm there are no network endpoints beyond common checks (google.com, Telegram endpoints) and no unexpected remote uploads.

Emergency recovery tool for OpenClaw. Diagnoses and fixes unresponsive bots via SSH.

Install

The script is bundled at scripts/sos.sh. Install locally:

cp scripts/sos.sh /usr/local/bin/sos
chmod +x /usr/local/bin/sos

To install on a remote machine:

scp scripts/sos.sh root@<IP>:/usr/local/bin/sos
ssh root@<IP> "chmod +x /usr/local/bin/sos"

Alternative — install from GitHub:

curl -fsSL https://raw.githubusercontent.com/clawsos/claw-sos/main/install.sh | bash

Usage

Interactive (human via SSH)

sos          # whiptail arrow-key menu

Non-interactive (agent or cron)

sos auto     # autofix: diagnose → doctor → restart → force → nuclear
sos net      # network check only
sos tg       # telegram test message
sos --version
sos --help

When the bot is down — decision tree

1. Run sos auto — handles 95% of cases automatically
2. If autofix fails → run sos net — if network is broken, fix DNS/internet first
3. If network is fine but bot still down → run sos tg — check Telegram delivery
4. If Telegram fails → check bot token validity
5. Last resort → sos menu option 9 (Nuclear) — kills everything and starts fresh

Menu Options

#	Name	What it does	Safe?
1	Check status	Gateway running, RAM, disk, version	✅ Read-only
2	Restart	Graceful restart	✅ Safe
3	Force kill	Kill process + restart	⚠️ Drops active sessions
4	Rollback	Revert to previous version + config	⚠️ Downgrade
5	View logs	Last 50 lines of gateway log	✅ Read-only
6	Full diagnostic	RAM, disk, Telegram, sessions, process	✅ Read-only
7	Backup config	Save config + version before changes	✅ Safe
8	Self-test	Verify SOS script works	✅ Read-only
9	Nuclear	Kill ALL openclaw processes, reload	🔴 Last resort
10	Autofix	Escalating auto-repair	⚠️ May restart
11	Network check	DNS, internet, Telegram API, Anthropic	✅ Read-only
12	Telegram test	Send real test message	✅ Safe

Autofix Escalation Order

1. Diagnose: process, RAM, disk
2. Clean RAM/disk if critical
3. openclaw doctor --fix
4. Graceful restart → wait 15s → check
5. Force kill + restart → wait 15s → check
6. Nuclear (kill all + reload)

Stops as soon as gateway is healthy.

Log Location

All actions logged to ~/.openclaw/backups/sos.log. Read this to understand what happened during recovery:

cat ~/.openclaw/backups/sos.log

Platform Support

• Linux: Full support (systemd, journalctl, free, /proc)
• macOS: Full support (launchctl, log show, vm_stat, purge, dialog fallback)
• Docker: Partial — no systemd, manual fallback works

Credentials

This skill uses no API keys or tokens of its own. It reads existing OpenClaw config to:

• Check gateway status (local process, no network)
• Send Telegram test messages (uses the bot token already configured in openclaw.json)
• Check Anthropic API reachability (HTTPS ping only, no auth)

No credentials are stored, transmitted, or required to install or run SOS.

Source

GitHub: https://github.com/clawsos/claw-sos