Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

restart-task-recovery重启任务恢复

Agent Skill

restart-task-recovery 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,278

周安装

379

GitHub Stars

公开资料未说明

下载量

3,002
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:restart-task-recovery(重启任务恢复)
来源仓库:https://github.com/swiftking100/restart-task-recovery
安装命令:
openclaw skills install restart-task-recovery
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install restart-task-recovery

简介

restart-task-recovery 在 OpenClaw 重启期间保留并恢复多代理协作任务的状态。

  • 适用于 OpenClaw 环境,支持跨会话的任务接力与资源复用。
  • 通过持久化作业调度实现无缝恢复,减少重复工作量。
  • 使用前需确认任务是否支持断点续传,避免状态冲突。
  • 建议仅在必要重启时使用,并验证恢复后行为一致性。

SKILL.md

name
restart-task-recovery
description
Preserve and resume in-progress multi-agent work across OpenClaw config patch/apply restarts. Use when a restart is required during active tasks, when users ask to minimize interruption, or when agent runs/tool calls were interrupted by gateway restart/timeouts.

Restart Task Recovery

Use this workflow to maximize successful recovery after OpenClaw restart.

1) Pre-restart checkpoint (required)

Before any gateway.config.patch, gateway.config.apply, gateway.update.run, or gateway.restart:

  1. List active sessions that may be impacted (sessions_list).
  2. For each active work session, capture the latest context (sessions_history, limit 20-50).
  3. Write a compact checkpoint file at:

- memory/restart-checkpoints/<YYYY-MM-DD>/<HHmmss>.md

  1. Include per session:

- sessionKey / label / agent - goal - last completed step - next exact step - blocked dependencies (if any) - a ready-to-send resume message (1-2 lines)

Keep checkpoint concise and executable.

2) Restart with explicit recovery intent

When calling gateway restart/config change, set note to include recovery intent, e.g.:

  • “配置已更新并重启;将按 checkpoint 恢复中断任务。”

3) Post-restart recovery sweep

After restart:

  1. Re-list sessions (sessions_list) and compare against checkpoint.
  2. For each interrupted/idle target session, send resume message via sessions_send:

- “Continue where you left off. Last completed: <x>. Next: <y>. If previous tool call failed, retry from <y>.”

  1. Do not poll in tight loops. Check on-demand only.
  2. Summarize recovery status to user:

- recovered sessions - still blocked sessions - manual follow-up needed

4) Idempotent task design rules

When resuming tasks, enforce:

  1. Re-run-safe steps (idempotency key / upsert / duplicate-safe writes).
  2. Small step boundaries with explicit “done markers”.
  3. External writes batched, not one-by-one loops.
  4. On uncertainty, verify state first then continue.

5) V2 automation helper

Use script: scripts/build_checkpoint.py to generate checkpoint markdown from structured JSON.

Example:

cat session-snapshot.json | python3 scripts/build_checkpoint.py memory/restart-checkpoints/$(date +%F)/$(date +%H%M%S).md

Expected stdin JSON shape:

{
  "sessions": [
    {
      "sessionKey": "agent:engineer:main",
      "agentId": "engineer",
      "goal": "Finish regression verification",
      "lastDone": "401/幂等/时区/retention case passed",
      "nextStep": "Publish final acceptance summary",
      "blockers": "none"
    }
  ]
}

6) V3 resume-plan automation

Use script: scripts/generate_resume_plan.py to parse the latest checkpoint and produce a structured resume plan.

Example:

python3 scripts/generate_resume_plan.py memory/restart-checkpoints/2026-03-09/162200.md /tmp/resume-plan.json

Then send each items[].resumeMessage to items[].sessionKey via sessions_send.

Rules:

  • Send once per session (no loop polling).
  • If a session is already active and progressing, skip resend.
  • After sends, post one concise recovery summary to user.

7) V4 one-click recovery payload generator

Use script: scripts/recover_from_latest_checkpoint.py.

It auto-selects the latest checkpoint file and emits a ready JSON payload list for sessions_send calls.

Examples:

# Use latest checkpoint automatically
python3 scripts/recover_from_latest_checkpoint.py > /tmp/recover-actions.json

# Use a specific checkpoint
python3 scripts/recover_from_latest_checkpoint.py memory/restart-checkpoints/2026-03-09/162200.md > /tmp/recover-actions.json

Execution guidance:

  • Read /tmp/recover-actions.json
  • Execute each actions[] item with sessions_send
  • Post one concise summary to user

8) V5 pre-resume verifier + manual confirmation gate

Use script: scripts/pre_resume_verify.py to score resume actions before sending.

Examples:

python3 scripts/pre_resume_verify.py /tmp/recover-actions.json /tmp/recover-verified.json

Behavior:

  • Marks each action as risk=normal|high
  • high risk actions are set to decision=hold and requiresManualConfirm=true
  • Only send decision=send automatically
  • Ask user confirmation before executing held actions

Recommended execution flow:

  1. Generate actions with V4
  2. Verify with V5
  3. Send all decision=send
  4. Present decision=hold list to user for explicit confirmation

9) V6 execution-plan generator (auto-send safe items)

Use script: scripts/execute_verified_recovery.py with V5 output.

Example:

python3 scripts/execute_verified_recovery.py /tmp/recover-verified.json > /tmp/recover-exec.json

Behavior:

  • Emits sendActions[] for auto-safe resumes (decision=send)
  • Emits holdForManualConfirm[] for risky resumes (decision=hold)

Execution:

  1. Execute all sendActions[] with sessions_send
  2. Ask user to confirm holdForManualConfirm[]
  3. Execute confirmed held items
  4. Post concise summary

10) Message templates

Read and use: references/templates.md

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

72.96%
按下载量换算2,190

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills