How do I install the Claw Sos skill?

Run npx skillmds@latest add lord1egypt/claw-sos in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claw Sos safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: WARNING. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claw Sos?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claw Sos free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claw Sos?

Lord1Egypt (@lord1egypt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claw Sos by lord1egypt — Agent Skill

Name: Claw Sos
Rating: 4.2 (5 reviews)
Author: Lord1Egypt

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 diagnosis or recovery, (2) you need to install SOS on a new or existing machine, (3) autofix, rollback, network check, or Telegram test is needed, (4) the user mentions "sos", "recovery", "bot is down", "not responding", or "emergency fix".

Lord1Egypt Updated Sep 8, 2026 2 repo stars

File contents

claw-sos

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

Run sos auto — handles 95% of cases automatically
If autofix fails → run sos net — if network is broken, fix DNS/internet first
If network is fine but bot still down → run sos tg — check Telegram delivery
If Telegram fails → check bot token validity
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

Diagnose: process, RAM, disk
Clean RAM/disk if critical
openclaw doctor --fix
Graceful restart → wait 15s → check
Force kill + restart → wait 15s → check
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

---name: claw-sosdescription: Install, run, and manage the SOS emergency recovery tool for OpenClaw instances. Use when (1) the bot stops responding on Telegram/Discord and needs diagnosis or recovery, (2) you need to install SOS on a new or existing machine, (3) autofix, rollback, network check, or Telegram test is needed, (4) the user mentions "sos", "recovery", "bot is down", "not responding", or "emergency fix".---# claw-sosEmergency recovery tool for OpenClaw. Diagnoses and fixes unresponsive bots via SSH.## InstallThe script is bundled at `scripts/sos.sh`. Install locally:```bashcp scripts/sos.sh /usr/local/bin/soschmod +x /usr/local/bin/sos```To install on a remote machine:```bashscp scripts/sos.sh root@<IP>:/usr/local/bin/sosssh root@<IP> "chmod +x /usr/local/bin/sos"```Alternative — install from GitHub:```bashcurl -fsSL https://raw.githubusercontent.com/clawsos/claw-sos/main/install.sh | bash```## Usage### Interactive (human via SSH)```bashsos # whiptail arrow-key menu```### Non-interactive (agent or cron)```bashsos auto # autofix: diagnose → doctor → restart → force → nuclearsos net # network check onlysos tg # telegram test messagesos --versionsos --help```### When the bot is down — decision tree1. Run `sos auto` — handles 95% of cases automatically2. If autofix fails → run `sos net` — if network is broken, fix DNS/internet first3. If network is fine but bot still down → run `sos tg` — check Telegram delivery4. If Telegram fails → check bot token validity5. 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 Order1. Diagnose: process, RAM, disk2. Clean RAM/disk if critical3. `openclaw doctor --fix`4. Graceful restart → wait 15s → check5. Force kill + restart → wait 15s → check6. Nuclear (kill all + reload)Stops as soon as gateway is healthy.## Log LocationAll actions logged to `~/.openclaw/backups/sos.log`. Read this to understand what happened during recovery:```bashcat ~/.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## CredentialsThis 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.## SourceGitHub: https://github.com/clawsos/claw-sos

Frequently asked questions