Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Productivity
Task Resume
Automatic interrupted-task resume workflow with queueing and recovery. Use when a user asks to resume interrupted work after temporary context switches, prot...
skill openclawclawhub Free
Automatic interrupted-task resume workflow with queueing and recovery. Use when a user asks to resume interrupted work after temporary context switches, prot...
β¬ 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
- README.md, SKILL.md, scripts/task_resume_queue.py
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.3.0
Provenance
- Publisher
- RichardSun700
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Task Resume
Use this skill to ensure interrupted tasks are recovered automatically.
Defaults (MANDATORY)
Make interruption enqueue the default behavior. On any non-explicit context switch, auto-enqueue the active unfinished task. Enqueue at message-time (immediately when interruption is detected), not only on periodic checks. Use one shared queue file for all sessions/clones so the view is unified.
Rules
Treat user-explicit commands (cancel, pause, change priority, do it tomorrow) as overrides. Treat all other topic switches as potential interruptions. Before switching topics, persist interruption context to queue. After completing the active task, immediately resume the oldest queued interrupted task. If queue is empty, do nothing.
Shared Queue Storage (cross-session)
Canonical queue file: memory/task-resume-queue.json This file is workspace-global and shared across main + clone + group sessions. Always pass source with session/channel identity. Use helper script: scripts/task_resume_queue.py
Interruption Detection
Consider a task interrupted when all are true: There is an active task with unfinished acceptance criteria. A new user request is unrelated to finishing that active task. User did not explicitly cancel/pause/defer the active task.
Message-Time Enforcement (required)
Before handling every new user message: Check whether an active task exists and is unfinished. If the incoming message is an unrelated request and no explicit override is present, enqueue immediately. Only then switch to the new request. This prevents queue misses caused by timing gaps.
Log-based Recovery (ENOENT-safe)
When recovery needs session .jsonl context, use: python3 skills/task-resume/scripts/task_resume_queue.py recover \ --log "~/.openclaw/agents/main/sessions/<session>.jsonl" \ --title "<active task title>" \ --acceptance "<acceptance criteria>" \ --source "<channel>" \ --session "<session_key_or_chat_id>" If the log file is missing (ENOENT), treat it as expected and continue (skipped_missing_log), do not raise alert-level failure.
On Interruption (auto-enqueue)
Run immediately at interruption detection: python3 skills/task-resume/scripts/task_resume_queue.py add \ --title "<active task title>" \ --context "<what was done + exact next step>" \ --acceptance "<acceptance criteria>" \ --source "<channel>" \ --session "<session_key_or_chat_id>" Then acknowledge briefly: queued + will auto-resume.
On Active Task Completion (resume)
Run: python3 skills/task-resume/scripts/task_resume_queue.py pop If one item is returned, resume it immediately and announce: Resuming previously interrupted task: <title>. If empty, continue normal flow.
Unified View
Run: python3 skills/task-resume/scripts/task_resume_queue.py status This returns total queue count + grouped counts by source/session.
Guardrails
Never drop queued tasks silently. Always include next-step quality context when enqueueing. Deduplicate: if same task title and near-identical context exists in queue, update timestamp instead of appending. Keep queue max size 30; discard oldest overflow items after logging to memory/YYYY-MM-DD.md.
Watchdog Auto-Continue (Heartbeat/Cron)
When users require "not just reminder, but auto-continue execution", add a watchdog cron policy: Run every 30 minutes. First inspect unfinished primary task + queue status. If interrupted or no recent progress, immediately continue the next actionable step. Send concise progress each run: done / in-progress / next step + ETA. Even with no material change, send a shortε·‘ζ£εζ§οΌ"ε·²ε·‘ζ£οΌη»§η»ζ§θ‘δΈ"οΌ. Recommended cron shape for delivery reliability: Prefer sessionTarget="main" + payload.kind="systemEvent" for user-facing continuity checks. Avoid fragile announce-only chains when delivery channel config is unstable.
Daily Hygiene
At least once daily: python3 skills/task-resume/scripts/task_resume_queue.py list If stale items (>7 days), ask user whether to cancel or schedule.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs1 Scripts
- SKILL.md
- README.md
- scripts/task_resume_queue.py