{ "schemaVersion": "1.0", "item": { "slug": "deadclaw", "name": "DeadClaw", "source": "tencent", "type": "skill", "category": "其他", "sourceUrl": "https://clawhub.ai/Kintupercy/deadclaw", "canonicalUrl": "https://clawhub.ai/Kintupercy/deadclaw", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/deadclaw", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=deadclaw", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "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" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/deadclaw" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/deadclaw", "agentPageUrl": "https://openagent3.xyz/skills/deadclaw/agent", "manifestUrl": "https://openagent3.xyz/skills/deadclaw/agent.json", "briefUrl": "https://openagent3.xyz/skills/deadclaw/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "DeadClaw — Emergency Kill Switch for OpenClaw Agents", "body": "\"One tap. Everything stops.\"\n\nDeadClaw is a single-purpose emergency kill switch. When triggered, it immediately\nhalts all running OpenClaw agent processes, stops Docker containers, pauses all\nscheduled cron jobs and heartbeats, kills all active sessions, and writes a\ntimestamped incident log. It then confirms back to whichever surface triggered it.\n\nWorks with both native OpenClaw installs and Docker-based deployments\n(Hostinger VPS, etc.). Auto-detects your setup." }, { "title": "Why DeadClaw Exists", "body": "The ClawHavoc attack (February 2026) exposed 1,184 malicious skills in the OpenClaw\necosystem. People run agents autonomously — often overnight, often unattended. When\nsomething goes wrong, you need a way to stop everything from wherever you are, even\nfrom your phone. DeadClaw is that way." }, { "title": "Activation Methods", "body": "DeadClaw supports three activation methods. All three execute the exact same kill\nsequence — the only difference is how the user triggers it." }, { "title": "Method 1: Message Trigger", "body": "The user sends a trigger word to any connected OpenClaw channel (Telegram, WhatsApp,\nDiscord, Slack, or any other connected channel). The following words activate DeadClaw:\n\nkill or KILL\ndead\nstop everything\nemergency stop\ndeadclaw\n🔴\n\nWhen a trigger word is detected:\n\nExecute scripts/kill.sh from the DeadClaw skill directory\nCapture the output (process count, containers stopped, cron jobs paused, timestamp)\nSend confirmation back to the same channel the trigger came from:\n🔴 DeadClaw activated. All agents stopped. [timestamp] — [X] killed ([X] processes, [X] containers). [X] cron jobs paused. See deadclaw.log for full report." }, { "title": "Method 2: WebChat Kill Button", "body": "A persistent red button rendered in the OpenClaw WebChat dashboard. The HTML widget\nis located at ui/deadclaw-button.html. It calls kill.sh via OpenClaw's WebChat\nAPI hooks (window.OpenClaw.exec()). If the WebChat hooks are unavailable, the\nbutton degrades to showing an error message with manual instructions.\n\nTo embed the button, use OpenClaw's WebChat customization hooks:\n\nOpenClaw.WebChat.registerWidget('deadclaw-button', {\n src: 'skills/deadclaw/ui/deadclaw-button.html',\n position: 'top-bar',\n persistent: true\n});" }, { "title": "Method 3: Phone Home Screen Shortcut", "body": "A pre-built shortcut that sends the kill trigger message (deadclaw) to the user's\nconfigured Telegram bot. Setup guides for iOS and Android are in docs/:\n\ndocs/iphone-shortcut-guide.md — iOS Shortcuts setup\ndocs/android-widget-guide.md — Android widget setup (Tasker or HTTP Shortcuts)" }, { "title": "Watchdog (Passive Protection)", "body": "DeadClaw includes a background watchdog (scripts/watchdog.sh) that monitors for\ndangerous conditions and auto-triggers the kill without any user action.\n\nThe watchdog checks every 60 seconds for (after a 5-minute startup grace period):\n\nRunaway loops — Any agent process or Docker session running longer than 30 minutes\nToken burn — Token spend exceeding 50,000 tokens in under 10 minutes\nUnauthorized network — Outbound network calls to domains not on the user's whitelist\nSandbox escape — Any process attempting to write outside the designated OpenClaw workspace\n\nThe watchdog uses zero AI tokens — all checks use local system commands only.\n\nWhen the watchdog auto-triggers, it sends an alert explaining the reason:\n🔴 DeadClaw auto-triggered. Reason: [specific reason]. All processes stopped. Check deadclaw.log." }, { "title": "Watchdog Configuration", "body": "The watchdog reads its thresholds from environment variables (with sensible defaults):\n\nVariableDefaultDescriptionDEADCLAW_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\n\nStart the watchdog:\n\nscripts/watchdog.sh start\n\nStop the watchdog:\n\nscripts/watchdog.sh stop" }, { "title": "Status Check", "body": "User sends status to any connected channel. DeadClaw responds with a plain-English\nhealth report by executing scripts/status.sh:\n\nWhat agents are currently running (name, PID, uptime)\nCurrent token spend rate\nWhether the watchdog is active\nAny warnings about approaching thresholds" }, { "title": "Restore After Kill", "body": "User sends restore to any connected channel. DeadClaw executes scripts/restore.sh,\nwhich:\n\nShows what will be restored (backed-up crontab entries, stopped Docker containers, disabled services)\nPrompts: \"Restore [X] cron jobs from backup taken at [timestamp]? (yes/no)\"\nRestores the crontab from the most recent backup\nRestarts stopped OpenClaw Docker containers\nDetects the OpenClaw gateway\nConfirms restoration with a summary\n\nThe watchdog does NOT auto-start after restore — the user verifies stability first,\nthen starts it manually with scripts/watchdog.sh start." }, { "title": "Scripts Reference", "body": "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\n\nAll scripts support a --dry-run flag that logs what would happen without taking action." }, { "title": "Incident Log", "body": "All kill events are logged to deadclaw.log in the skill directory. Each entry\nrecords: timestamp, trigger source (channel name), trigger method (message/button/\nwatchdog/auto), processes killed (count and PIDs), Docker containers stopped, cron\njobs paused, and token spend at time of kill. The log is append-only and never\nautomatically cleared." }, { "title": "Platform Support", "body": "DeadClaw works on both Linux (VPS, bare metal) and macOS (Mac Mini, MacBook).\nScripts auto-detect the OS and use the appropriate commands:\n\nLinux: systemctl for services, pgrep for processes, Docker support\nmacOS: launchctl for agents, pgrep for processes, Docker support" } ], "body": "DeadClaw — Emergency Kill Switch for OpenClaw Agents\n\n\"One tap. Everything stops.\"\n\nDeadClaw 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.\n\nWorks with both native OpenClaw installs and Docker-based deployments (Hostinger VPS, etc.). Auto-detects your setup.\n\nWhy DeadClaw Exists\n\nThe 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.\n\nActivation Methods\n\nDeadClaw supports three activation methods. All three execute the exact same kill sequence — the only difference is how the user triggers it.\n\nMethod 1: Message Trigger\n\nThe user sends a trigger word to any connected OpenClaw channel (Telegram, WhatsApp, Discord, Slack, or any other connected channel). The following words activate DeadClaw:\n\nkill or KILL\ndead\nstop everything\nemergency stop\ndeadclaw\n🔴\n\nWhen a trigger word is detected:\n\nExecute scripts/kill.sh from the DeadClaw skill directory\nCapture the output (process count, containers stopped, cron jobs paused, timestamp)\nSend 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.\nMethod 2: WebChat Kill Button\n\nA 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.\n\nTo embed the button, use OpenClaw's WebChat customization hooks:\n\nOpenClaw.WebChat.registerWidget('deadclaw-button', {\n src: 'skills/deadclaw/ui/deadclaw-button.html',\n position: 'top-bar',\n persistent: true\n});\n\nMethod 3: Phone Home Screen Shortcut\n\nA 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/:\n\ndocs/iphone-shortcut-guide.md — iOS Shortcuts setup\ndocs/android-widget-guide.md — Android widget setup (Tasker or HTTP Shortcuts)\nWatchdog (Passive Protection)\n\nDeadClaw includes a background watchdog (scripts/watchdog.sh) that monitors for dangerous conditions and auto-triggers the kill without any user action.\n\nThe watchdog checks every 60 seconds for (after a 5-minute startup grace period):\n\nRunaway loops — Any agent process or Docker session running longer than 30 minutes\nToken burn — Token spend exceeding 50,000 tokens in under 10 minutes\nUnauthorized network — Outbound network calls to domains not on the user's whitelist\nSandbox escape — Any process attempting to write outside the designated OpenClaw workspace\n\nThe watchdog uses zero AI tokens — all checks use local system commands only.\n\nWhen the watchdog auto-triggers, it sends an alert explaining the reason: 🔴 DeadClaw auto-triggered. Reason: [specific reason]. All processes stopped. Check deadclaw.log.\n\nWatchdog Configuration\n\nThe watchdog reads its thresholds from environment variables (with sensible defaults):\n\nVariable\tDefault\tDescription\nDEADCLAW_MAX_RUNTIME_MIN\t30\tMax agent runtime in minutes before auto-kill\nDEADCLAW_MAX_TOKENS\t50000\tMax token spend in the monitoring window\nDEADCLAW_TOKEN_WINDOW_MIN\t10\tToken spend monitoring window in minutes\nDEADCLAW_WHITELIST\t./network-whitelist.txt\tAllowed outbound domains (one per line)\nDEADCLAW_WORKSPACE\t$OPENCLAW_WORKSPACE\tDesignated workspace directory\n\nStart the watchdog:\n\nscripts/watchdog.sh start\n\n\nStop the watchdog:\n\nscripts/watchdog.sh stop\n\nAdditional Commands\nStatus Check\n\nUser sends status to any connected channel. DeadClaw responds with a plain-English health report by executing scripts/status.sh:\n\nWhat agents are currently running (name, PID, uptime)\nCurrent token spend rate\nWhether the watchdog is active\nAny warnings about approaching thresholds\nRestore After Kill\n\nUser sends restore to any connected channel. DeadClaw executes scripts/restore.sh, which:\n\nShows what will be restored (backed-up crontab entries, stopped Docker containers, disabled services)\nPrompts: \"Restore [X] cron jobs from backup taken at [timestamp]? (yes/no)\"\nRestores the crontab from the most recent backup\nRestarts stopped OpenClaw Docker containers\nDetects the OpenClaw gateway\nConfirms restoration with a summary\n\nThe watchdog does NOT auto-start after restore — the user verifies stability first, then starts it manually with scripts/watchdog.sh start.\n\nScripts Reference\nScript\tPurpose\nscripts/kill.sh\tCore kill script — stops all agents + Docker containers, pauses cron, logs incident\nscripts/watchdog.sh\tBackground monitor daemon — auto-triggers kill on threshold breach\nscripts/status.sh\tHealth report — shows running agents, Docker containers, token spend, watchdog status\nscripts/restore.sh\tPost-kill recovery — restores crontab, restarts Docker containers\n\nAll scripts support a --dry-run flag that logs what would happen without taking action.\n\nIncident Log\n\nAll 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.\n\nPlatform Support\n\nDeadClaw works on both Linux (VPS, bare metal) and macOS (Mac Mini, MacBook). Scripts auto-detect the OS and use the appropriate commands:\n\nLinux: systemctl for services, pgrep for processes, Docker support\nmacOS: launchctl for agents, pgrep for processes, Docker support" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/Kintupercy/deadclaw", "publisherUrl": "https://clawhub.ai/Kintupercy/deadclaw", "owner": "Kintupercy", "version": "1.0.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/deadclaw", "downloadUrl": "https://openagent3.xyz/downloads/deadclaw", "agentUrl": "https://openagent3.xyz/skills/deadclaw/agent", "manifestUrl": "https://openagent3.xyz/skills/deadclaw/agent.json", "briefUrl": "https://openagent3.xyz/skills/deadclaw/agent.md" } }