← Back to Skills Marketplace
Resume After Gateway Restart
by
Bobby Lindsey
· GitHub ↗
· v1.0.0
· MIT-0
90
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install resume-after-gateway-restart
Description
Reliably resume work after `openclaw gateway restart` (or when you must restart the OpenClaw gateway mid-task). Uses durable one-shot cron `agentTurn` jobs (...
Usage Guidance
This skill appears to implement its stated purpose, but review these points before installing:
- The package metadata declares no required binaries, yet the scripts call: openclaw (sessions/cron), systemd-run/systemctl, and python3. Ensure those commands exist and are trusted on the host.
- The skill will schedule a systemd restart of openclaw-gateway and will create one-shot cron agentTurns that autonomously send messages back to captured channels. Only install if you trust the skill to act on your behalf and your environment supports systemd and the openclaw CLI.
- Inspect memory/post-restart-task.md usage: the resume job will read and append to this file. Ensure storing sensitive data there is acceptable.
- Test in a safe environment first (or dry-run the scheduling steps without performing the restart) to confirm route/model inference works for your sessionKey format.
If you want to proceed, ask the author to update package metadata to list required binaries (openclaw, systemd, python3) and to document failure modes when systemd isn't available. If you do not trust autonomous restarts or automated sends to chat channels, do not install.
Capability Analysis
Type: OpenClaw Skill
Name: resume-after-gateway-restart
Version: 1.0.0
This skill bundle provides a mechanism for the agent to restart the OpenClaw gateway service and resume tasks using scheduled cron jobs. It utilizes scripts like `delayed-gateway-restart.sh` (using `systemd-run` to trigger `systemctl restart`) and `schedule-resume-cron.sh` (using `openclaw cron` to schedule automated follow-up turns). While the logic is transparent and directly supports the stated goal of session continuity, the inherent capabilities—restarting system services and scheduling persistent automated execution—are high-risk behaviors that warrant a suspicious classification despite the lack of clear malicious intent.
Capability Assessment
Purpose & Capability
The skill's behavior (scheduling cron agentTurns, reading/writing memory/post-restart-task.md, calling openclaw sessions/cron, and using systemd-run/systemctl) is coherent with 'resume after gateway restart'. However the registry metadata claims no required binaries/configs while the scripts clearly require: the openclaw CLI, systemd (systemd-run and systemctl), and python3. The missing declared dependencies is an incoherence the user should note.
Instruction Scope
SKILL.md stays within the stated scope: it instructs capturing session/delivery info, writing a post-restart memory file, scheduling two isolated agentTurn cron jobs (a 'back' message and a resume job), and then scheduling a delayed restart. It explicitly reads and writes memory/post-restart-task.md and uses openclaw sessions/cron — these are expected for this purpose. The instructions do grant the agent autonomous ability to send messages after restart (intended behavior).
Install Mechanism
No install spec (instruction-only plus two helper scripts) — low installation risk. The scripts are bundled with the skill and not downloaded from external URLs.
Credentials
No environment variables or external credentials are requested, which aligns with the described function. However, the scripts do require runtime tools (openclaw, systemd, python3) that were not declared in the registry metadata — this omission should be treated as a configuration/packaging problem rather than malicious intent.
Persistence & Privilege
always:false (normal). The skill schedules durable one-shot cron jobs and a transient systemd unit that will autonomously run agentTurns and restart the gateway. That autonomous behavior is part of the feature, but it increases blast radius (the agent will send messages and modify the memory file without a follow-up user step).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install resume-after-gateway-restart - After installation, invoke the skill by name or use
/resume-after-gateway-restart - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial publish of skill to resume activity after performing a gateway restart
Metadata
Frequently Asked Questions
What is Resume After Gateway Restart?
Reliably resume work after `openclaw gateway restart` (or when you must restart the OpenClaw gateway mid-task). Uses durable one-shot cron `agentTurn` jobs (... It is an AI Agent Skill for Claude Code / OpenClaw, with 90 downloads so far.
How do I install Resume After Gateway Restart?
Run "/install resume-after-gateway-restart" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Resume After Gateway Restart free?
Yes, Resume After Gateway Restart is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Resume After Gateway Restart support?
Resume After Gateway Restart is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Resume After Gateway Restart?
It is built and maintained by Bobby Lindsey (@bobbylindsey); the current version is v1.0.0.
More Skills