task-progress

Append date-stamped progress entries and maintain LRU task history for Hermes workflows.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill task-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-progress
Source: https://github.com/agentscope-ai/HiClaw/tree/main/manager/agent/hermes-worker-agent/skills/task-progress
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill task-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task progress can get lost or become inconsistent after interruptions, making it hard to resume work, audit decisions, or understand what changed over time.

Core Features & Use Cases

  • Progress logging for meaningful actions: Append human-readable progress entries after each decision, sub-step completion, or issue to a date-stamped file under the task directory.
  • LRU task history for fast recovery: Maintain a top-10 most recently updated task-history.json, spilling older tasks to per-task history files to keep recovery lightweight.
  • Deterministic resume flow after session reset: Load the latest task state by reading history first, then pulling spec.md, plan.md, and the most recent progress entries to continue from the right point.

Use case example: An autonomous coordinator assigns a long-running task, the session resets midway, and you need to resume with full context by reconstructing the plan and decisions from the saved progress logs.

Quick Start

Ask the agent to record a progress update for task-id task-20260221-100000 by appending today’s date-stamped entry to the task’s progress log and updating ~/.hermes/task-history.json accordingly.

Frequently Asked Questions about task-progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a multi-agent task after a session reset?

To resume a multi-agent task after a session reset, load the latest state by reading task-history.json first, then pull spec.md, plan.md, and recent progress entries to continue from the correct point.

What is the best way to keep multi-agent task progress auditable?

Keeping task progress auditable requires appending human-readable, date-stamped progress entries to a log file under the shared task directory after every meaningful action, decision, or sub-step completion.

How does LRU task history work for shared filesystem workflows?

LRU task history maintains a top-10 most recently updated task-history.json file, spilling older tasks to per-task history files to keep recovery lightweight and fast.

Can I use a shared filesystem to coordinate task progress across multiple agents?

Yes, you can coordinate task progress across multiple agents using a shared filesystem by having agents append date-stamped entries to a shared progress log and updating a central task-history.json file.

Do I need to log every action for task progress to be resumable?

You need to push progress after every meaningful action, such as a decision or sub-step completion, ensuring the resumable state captures enough context to reconstruct the workflow.

Why are my resumed tasks missing the latest progress entries?

Resumed tasks miss latest progress entries if the deterministic resume flow is not followed correctly, such as failing to sort filenames properly or not reading task-history.json before pulling spec.md and plan.md.