Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Other
DeadClaw
Emergency kill switch for OpenClaw agents. Instantly halts all running agents, pauses scheduled jobs, kills active sessions, and logs everything — triggered...
skill openclawclawhub Free
Emergency kill switch for OpenClaw agents. Instantly halts all running agents, pauses scheduled jobs, kills active sessions, and logs everything — triggered...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- deadclaw/docs/android-widget-guide.md, deadclaw/docs/clawhub-listing.md, deadclaw/docs/competitive-notes.md, deadclaw/docs/iphone-shortcut-guide.md, deadclaw/docs/launch-post.md, deadclaw/docs/roadmap.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- Kintupercy
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
DeadClaw — Emergency Kill Switch for OpenClaw Agents
"One tap. Everything stops." DeadClaw is a single-purpose emergency kill switch. When triggered, it immediately halts all running OpenClaw agent processes, stops Docker containers, pauses all scheduled cron jobs and heartbeats, kills all active sessions, and writes a timestamped incident log. It then confirms back to whichever surface triggered it. Works with both native OpenClaw installs and Docker-based deployments (Hostinger VPS, etc.). Auto-detects your setup.
Why DeadClaw Exists
The ClawHavoc attack (February 2026) exposed 1,184 malicious skills in the OpenClaw ecosystem. People run agents autonomously — often overnight, often unattended. When something goes wrong, you need a way to stop everything from wherever you are, even from your phone. DeadClaw is that way.
Activation Methods
DeadClaw supports three activation methods. All three execute the exact same kill sequence — the only difference is how the user triggers it.
Method 1: Message Trigger
The user sends a trigger word to any connected OpenClaw channel (Telegram, WhatsApp, Discord, Slack, or any other connected channel). The following words activate DeadClaw: kill or KILL dead stop everything emergency stop deadclaw 🔴 When a trigger word is detected: Execute scripts/kill.sh from the DeadClaw skill directory Capture the output (process count, containers stopped, cron jobs paused, timestamp) Send confirmation back to the same channel the trigger came from: 🔴 DeadClaw activated. All agents stopped. [timestamp] — [X] killed ([X] processes, [X] containers). [X] cron jobs paused. See deadclaw.log for full report.
Method 2: WebChat Kill Button
A persistent red button rendered in the OpenClaw WebChat dashboard. The HTML widget is located at ui/deadclaw-button.html. It calls kill.sh via OpenClaw's WebChat API hooks (window.OpenClaw.exec()). If the WebChat hooks are unavailable, the button degrades to showing an error message with manual instructions. To embed the button, use OpenClaw's WebChat customization hooks: OpenClaw.WebChat.registerWidget('deadclaw-button', { src: 'skills/deadclaw/ui/deadclaw-button.html', position: 'top-bar', persistent: true });
Method 3: Phone Home Screen Shortcut
A pre-built shortcut that sends the kill trigger message (deadclaw) to the user's configured Telegram bot. Setup guides for iOS and Android are in docs/: docs/iphone-shortcut-guide.md — iOS Shortcuts setup docs/android-widget-guide.md — Android widget setup (Tasker or HTTP Shortcuts)
Watchdog (Passive Protection)
DeadClaw includes a background watchdog (scripts/watchdog.sh) that monitors for dangerous conditions and auto-triggers the kill without any user action. The watchdog checks every 60 seconds for (after a 5-minute startup grace period): Runaway loops — Any agent process or Docker session running longer than 30 minutes Token burn — Token spend exceeding 50,000 tokens in under 10 minutes Unauthorized network — Outbound network calls to domains not on the user's whitelist Sandbox escape — Any process attempting to write outside the designated OpenClaw workspace The watchdog uses zero AI tokens — all checks use local system commands only. When the watchdog auto-triggers, it sends an alert explaining the reason: 🔴 DeadClaw auto-triggered. Reason: [specific reason]. All processes stopped. Check deadclaw.log.
Watchdog Configuration
The watchdog reads its thresholds from environment variables (with sensible defaults): VariableDefaultDescriptionDEADCLAW_MAX_RUNTIME_MIN30Max agent runtime in minutes before auto-killDEADCLAW_MAX_TOKENS50000Max token spend in the monitoring windowDEADCLAW_TOKEN_WINDOW_MIN10Token spend monitoring window in minutesDEADCLAW_WHITELIST./network-whitelist.txtAllowed outbound domains (one per line)DEADCLAW_WORKSPACE$OPENCLAW_WORKSPACEDesignated workspace directory Start the watchdog: scripts/watchdog.sh start Stop the watchdog: scripts/watchdog.sh stop
Status Check
User sends status to any connected channel. DeadClaw responds with a plain-English health report by executing scripts/status.sh: What agents are currently running (name, PID, uptime) Current token spend rate Whether the watchdog is active Any warnings about approaching thresholds
Restore After Kill
User sends restore to any connected channel. DeadClaw executes scripts/restore.sh, which: Shows what will be restored (backed-up crontab entries, stopped Docker containers, disabled services) Prompts: "Restore [X] cron jobs from backup taken at [timestamp]? (yes/no)" Restores the crontab from the most recent backup Restarts stopped OpenClaw Docker containers Detects the OpenClaw gateway Confirms restoration with a summary The watchdog does NOT auto-start after restore — the user verifies stability first, then starts it manually with scripts/watchdog.sh start.
Scripts Reference
ScriptPurposescripts/kill.shCore kill script — stops all agents + Docker containers, pauses cron, logs incidentscripts/watchdog.shBackground monitor daemon — auto-triggers kill on threshold breachscripts/status.shHealth report — shows running agents, Docker containers, token spend, watchdog statusscripts/restore.shPost-kill recovery — restores crontab, restarts Docker containers All scripts support a --dry-run flag that logs what would happen without taking action.
Incident Log
All kill events are logged to deadclaw.log in the skill directory. Each entry records: timestamp, trigger source (channel name), trigger method (message/button/ watchdog/auto), processes killed (count and PIDs), Docker containers stopped, cron jobs paused, and token spend at time of kill. The log is append-only and never automatically cleared.
Platform Support
DeadClaw works on both Linux (VPS, bare metal) and macOS (Mac Mini, MacBook). Scripts auto-detect the OS and use the appropriate commands: Linux: systemctl for services, pgrep for processes, Docker support macOS: launchctl for agents, pgrep for processes, Docker support
Category context
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- deadclaw/docs/android-widget-guide.md
- deadclaw/docs/clawhub-listing.md
- deadclaw/docs/competitive-notes.md
- deadclaw/docs/iphone-shortcut-guide.md
- deadclaw/docs/launch-post.md
- deadclaw/docs/roadmap.md