🧪

Stop Losing Long OpenClaw Runs: Task Tracker Saves a Resumable Work State

A community OpenClaw skill candidate that keeps a compact memory/tasks.md state snapshot for long-running or interrupted agent work. Not yet Runner-tested.

May 27, 2026
Original
Reachable skill source fileOpen original externally
Status & Access
Current access and latest update details.
Access
Free
Updated
Jun 1, 2026, 09:54 AM

LinkLoot AI review

Start skill only in isolation

Score: 69/100
Skill checked in isolation

Reviewed loot: Stop Losing Long OpenClaw Runs: Task Tracker Saves a Resumable Work State

My take: this skill has solid evidence: the linked skill sources were fetched, scanned statically, checked for Python imports and dependency surface, and stored as sandbox artifacts.

User decisionVerify first

My take: this skill has solid evidence: the linked skill sources were fetched, scanned statically, checked for Python imports and dependency surface, and stored as sandbox artifacts.

The visible value is plausible and easier to judge through source/screenshot evidence.Judges how careful a user should be when trying it: permissions, network use, dependencies, and hard warnings.
Reasons to use it
  • Keeps promise: The visible value is plausible and easier to judge through source/screenshot evidence.
  • Sources, external URL, and visible link/site signals were reviewed.
  • Install surface, scripts, dependencies, and suspicious patterns were checked statically.
  • Optional page snapshot. For code repositories this is context, not security proof.
Reasons to be careful
  • Useful with clear caveats; the scorecard reflects the concrete signals from this run.
  • The sandbox evidence reports executed=false and only the static step “Skill-Manifest statisch geprüft.” Users should not assume the automatic task tracking really works reliably or safely...
  • Safe to try: Judges how careful a user should be when trying it: permissions, network use, dependencies, and hard warnings.
  • Easy to try: Judges whether a normal user can repeat the first setup with reasonable effort.
Keeps promise82/100
Safe to try56/100
Easy to try59/100
Trust signals66/100
Worth following59/100
LLQI auditVerdict: RISKY
security & trust68/100
functionality & value58/100
quality & structure64/100
sources checked
code signals checked
snapshot optional
Dependencies checked

Automated AI review. Decision aid, not a safety guarantee. · 2026-06-01 04:51:51 UTC

What it does

Task Tracker is a community OpenClaw skill candidate that defines a compact memory/tasks.md state file for active work, background process metadata, progress notes, completion summaries, and failure records. The useful idea is simple: write a small resumable task snapshot before replying, so session resets or context compaction lose less operational state.

Who should use it

This is most relevant for operators running long multi-step OpenClaw sessions: deployments, browser tasks, media jobs, remote server work, or parallel background processes. It is less useful for short one-shot chats, and it should not replace a proper incident log, issue tracker, or durable job queue.

Setup surface

The reachable source surface appears to be SKILL.md-only, with no visible package install, binary, or external service requirement in the fetched source. It writes to a workspace memory file and relies on the agent following the documented format. Pricing evidence: no paid gate, API key, subscription, or commercial dependency was visible in the ClawHub/source pages inspected, so this Loot is tagged free.

Runner test plan

Before anyone treats this as usable, LinkLoot Runner AI Review should produce artifacts for:

  • Static scan of SKILL.md for instruction overreach, unsafe file paths, hidden prompts, broad reads/writes, and conflicts with existing OpenClaw memory rules.
  • Dependency/install review confirming whether the skill is documentation-only and whether installation changes any global/workspace behavior.
  • Prompt-injection/tool-poisoning review, especially because the source uses strong automatic trigger language like every task and write-before-reply.
  • Sandbox execution in a throwaway workspace covering task start, progress update, background-process note, completion, failure, pruning, and compaction-resume scenarios.
  • Screenshot/video evidence when command output, file diffs, or UI-visible task state exists.
  • Residual risks report covering stale task state, accidental leakage of commands/server names, conflict with existing memory policies, file-growth limits, and user confusion between task snapshots and audit logs.

Risk notes

This has not been installed, executed, imported, or tested on the Raspberry Pi. The claimed GitHub path from index pages was not reachable during this review, so the reachable ClawHub source-file endpoint is used as the verified source path. Because this skill changes agent operating behavior, Runner should verify it cannot override higher-priority instructions, leak sensitive process details, or write outside the intended workspace memory file. Do not call it safe, clean, production-ready, or recommended until Runner artifacts exist.

Source links

Discussion

Sign in to join the discussion and vote on comments.

No comments yet. Start the discussion.
Keep exploring

More from this topic

More in OpenClaw